VOGONS

Common searches


Reply 40 of 47, by dodleh

User metadata
Rank Newbie
Rank
Newbie

I have tested quite extensively this distro and it holds real potential. It is much more performance consistent than a typical DosBox running on top of a normal operating system, with multiple apps and background processes. Graphics and CPU emulation speed is nearly on par with Windows DosBox classic.

The graphics output quality and input lag are both very good, which is important when you resort to emulation.

I noticed and I understand why the distro works like that. First of all the distro is TCE (Tiny Core Linux with Extensions). It is a good choice. As far as I looked into the repository it seems that no newer Dosbox was released for the platform. Although it is quite difficult to customize, the DosBox configuration can be modified as needed if you go into the archives and search for obvious clues. The most important improvement, however, is to make the implementation of a recent Dosbox such as Dosbox-X in this distro.

Reply 41 of 47, by Peter z80.eu

User metadata
Rank Newbie
Rank
Newbie

A short question, I visted github, followed the dropbox link, and downloaded DBD_BETA.iso .
Then I tried to boot within VMware Workstation Player 16, and was surprised that the DOSBOX window at the end is soooo small.
Using the "fullscreen" option in VMware WP did not resized the DOSBOX window, still stayed in the same size.
Because the ISO starts straight into DOSBOX (without any stop in a linux shell), how can I influence the size of the DOSBOX window/screen ?

Reply 43 of 47, by Peter z80.eu

User metadata
Rank Newbie
Rank
Newbie

If I know what in VMWare listed Linux distro fits with the here choosen TinyCoreLinux (is it debian based?), I would try again. I've tested it with Ubuntu (as the preselection for the OS).
Also, I am not sure I would be able to install the VMware additions if there is no OS access (instead, just DOSBOX).

Reply 44 of 47, by Bhuthogg

User metadata
Rank Newbie
Rank
Newbie

Is there a way to make this boot straight to dbdmenu ? Or any way of automation into an exe/bat
I did try edit the SDA/dosbox/startup.bat but save failed
I was able to edit the sda1/dosbox/startup.bat but it made no difference.

I'm a bit lost to be honest as even putting the stick into a Linux distro doesn't show the SDA startup.bat 😂

Thanks

Reply 45 of 47, by mike_canada

User metadata
Rank Member
Rank
Member

My only thoughts on posting a direct image is whatever size drive I use, that’s the size the user would be stuck with unless they are comfortable with gparted or another partioning utility. Am I wrong?

I once made a boot CD that emulates a hard drive. It has a bunch of goodies on it including DOS. When it loaded, it loaded a ramdrive utility (can't remember the name now, but it wasn't XMSDSK because that didn't quite work with Windows 95 version of DOS). But the point of loading the ramdrive is to make access to the files faster. So essentially, on CD boot, all the files got copied over via xcopy or xcopy32 to the ramdrive. The entire contents weighed in at about 64MB.

Perhaps you can do a similar thing with your setup. when USB boots, check to see that the main hard drive exists then copy files over. but in DOSBOX the hard drive should exist anyway.

Another idea which could work is to use pkware's pkzip utility and zip2exe to make a DOS self-extracting image of the whole filesystem and save it as the EXE generated from zip2exe on the USB. This has the advantage of less bytes to transfer between devices (so somewhat of speed)