[Dosbox Megabuild 6 Dmg.zip

0 views

Skip to first unread message

Sharif Garmon

unread,

Jun 12, 2024, 6:55:08 AM6/12/24

to fretenexte

there is a trick to it that I once knew... Something to do with i/o address of joystick and so on... search for it here, maybe it was mentioned already. I'm sure I mentioned it,but probably in a removed thread. Also Win98 adds a nother layer of problems, it is even more unsupported as Windows 95.

Dosbox Megabuild 6 Dmg.zip

Download Zip --->>> https://t.co/nStxo0L5no

I'm asking this because I'm trying to access some files and folders on my iPad, but Windows 3.1 doesn't support long filenames, so it's impossible to really figure out what's going on (if someone knows a way of copying files with long filename support, then please tell!).

I was able to install Windows 95 just fine without making images, but I would get an error (SU992010) shortly after it finished copying the files (which took over 2 hours to complete). Trying to start it up with "win" results in a freeze.

Hopefully someone could shed some light if there's any way of having mounted drives show up in W95, or if there's a way of accessing long filenames files and folders from within DOS and getting them copied and whatnot.

Also, learn the philosophy of 'virtual machines' - getting pure mounted drives to show up for a whole nother operating system to control is dangerous. The least you could do is use Hal's megabuild and get native IPX support going so you can network your way to your folder, at least

DOS is limited to 8.3 filenames. Win3.x runs on top of DOS and inherits the limitation. I think some later versions of DOS, like the one you could boot with Win9X, had LFN support; but DOSBox does not emulate that DOS.

There is a utility program called "Instant File Access" (more info here) that adds support for long filenames in Win3.x. However, it maintains a database with a relationship between a long filename and the 8.3 filename used by DOS, and must first "learn" about that relationship before you will see the long filename in Windows, which is probably not exactly what you're looking for.

Thanks for the speedy response. First I tried Win 95C [OSR 2.5] and then Win95B [OSR 2.1]. Both of them gave the same error. As you note, however, these are the latest builds, so I'll give Win95A a go and post back.

Ok, I've tried Windows 95 [4.00.950] but am still receiving the "fatal exception OE" error upon booting. When I close dosbox and attempt to re-boot [ie. again type "imgmount c c.img" followed by "boot c.img"], it gives me:

So now it is no longer possible to even access the boot screen. Again, any suggestions will be much appreciated, but I'm getting the feeling no one has ever had this error, so it may be excessively difficult to solve.

Thanks for the inspiration dada - finally managed to crack it. The error appears to have came from the fact that I had two copies of dosbox - one mounted as a .dmg file while another on the Macintosh HDD. Running the one from the hard-drive produced the error, while running dosbox.img would create a flawless Win95 install. Pretty strange, but there was probably some conflict between the two.

Now just a final polishing-off query. Win95 is running with substantial graphical glitches. Reducing the display to 16 colors fixes the problem. I have read elsewhere [Windows 9x DOSBox Guide (Not officially supported)] the key to getting higher colors is installing the w950109b.zip drivers. However, how do I move the driver folder over to the Win95 operating environment? I tried mounting c.img and putting the files straight there, but it just corrupts the c.img file. Any ideas? Sorry for the rather noob question.

It's quite strange that you're getting graphical glitches. If you use machine=svga_s3 and cputype=pentium_slow (and possibly normal core) there shouldn't be any. I'm also running the OSX version, and in my case it works without any external drivers. But I guess you fixed that too, judging from your last post.

I've tried making Win95 a tad more useful by using a 2 gig hard-drive. Also, following other threads, I've installed win95c via "standard vga display" and "no sound," to circumvent the rundll32 error.

However, I've hit another dead end after trying to install daemon tools. Getting usb support in win95c was pretty straightforward, but then d-tools required the installing of internet explorer 4.0. but attempting to install IE4.0 always gave this error: