![]() I'm trying to install GeoWorks Ensemble 2.0 within DOSBox. I have five directories, each containing the contents of an install disk. I mounted the first disk as a floppy drive in DOSBox using these MOUNT parameters: mount a c: oldstuff geos2d1 -t floppy -l Geos_1 where 'Geos_1' is the volume label it will be expecting. GEOS (also later known as GeoWorks Ensemble, NewDeal Office and Breadbox. After release of Ensemble 2.01, GeoWorks dropped support for the desktop. GameLine permitted subscribers to temporarily download games and keep. I run the install program from the newly mounted A: drive, and it copies the first disk over, then asks for the second disk. I have no way of changing the mounts from within the install program. Fortunately, the Geoworks installer will let you escape to shell in the middle of installation. So I go there, do: mount -u a (unmounts drive A:) mount a c: oldstuff geos2d2 -t floppy -l Geos_2 and go back into the installer. But the installer isn't convinced that I really have disk 2 in my floppy drive. Any ideas as to why, or how I could work around this? Floppy installers for games and applications seem to be one area where DOSBox is rather rough going in the current version. Member Posts: 132 Joined: 2003-1-21 @ 23:13. I took a look with the debugger, and didn't see much of interest, and no special calls or anything when it came time to switch / detect floppies. Just in case it's useful, here's the output leading up to the install procedure, but again none of this occured near the floppy switch request: 19982865: FILES:Special file open command 40 file A: GEOWORKS.00: FILES:file create attributes 0 file C: AGEMOPLA AMMAGATL.EDZ 19989859: FILES:file create attributes 0 file C: ISFYZQVO.TWJ SWAPFILE.HDR 23952582: BIOS:INT15:Function 0x88 Remaining 0000 kb 24814638: DOSMISC:DOS:Unhandled call EA al=00. Red snapper making bones rarlab. Everything you want to know about healthy eating and cooking from our new book. Set al to default of 0 27270552: BIOS:INT15:Function 0x88 Remaining 0000 kb 28129123: DOSMISC:DOS:Unhandled call EA al=00. Set al to default of 0 32442834: MISC:DOS:Set File Attributes for c: VER.TMP not supported 35110932: MISC:MSCDEX: INT 2F 150B BX= 0000 CX=008: MISC:MSCDEX: INT 2F 150B BX= 0000 CX=003: MISC:MSCDEX: INT 2F 150B BX= 0000 CX=0000 Member Posts: 132 Joined: 2003-1-21 @ 23:13. I think this error is reminscent of the List-of-lists drivers that were partially implemented -- int 15/ Ah=8x, is trying to find free extended memory; On a hunch I suspect its probably trying to use Xenix/Dos 1/Unix7 device access, and freezing in the lists. Also, I recall that there was a few undocumented ints triggered by disk eject, (I cant remember the program that made it obvious at the moment; its was one of those where the disk-light stayed on, and prompted you to change disks. Non of that flashing/buzzing thing M$ made famous). Member Posts: 167 Joined: 2004-1-09 @ 00:09. 'asks for floppy' means it prints some 'press a key to continue' message, repeatedly if the wrong floppy is (mis)detected, right? ![]() Put some logging into dosbox, like at CPU_Interrupt (excluding those that annoy too much and are of no interest, like int8/int1c), and execute the app to that key press message thing. Then add a breakpoint to stuff like int16 or some code part that is right after the key detection. Check the interrupts that are called then (maybe some findfirst operations, possibly low-level disk routines, whatever). Maybe you can grab some idea of what could be wrong. DOSBox Author Posts: 10818 Joined: 2003-12-03 @ 21:23. Just out of curiousity, why are you trying to install Geoworks? I had purchased Ensemble 2.0 in the days of Windows 3.0 and installed it. To be honest I wasn't impressed. Ensemble was nothing more than a shell with AOL built-in and some included apps. Windows had 386 enchanced mode which allowed multi-tasking (I would be downloading with Telemate for DOS while playing MS Arcade). Ensemble would only multi-task it's own apps, when you went to DOS you had no access to Ensemble unless you quit your DOS app. The one impressive thing that kept me from erasing it from my hard drive was the print output. It had scalable fonts that produced near laser-like quatlity on my 9-pin Epson dot matrix. Sadly I loaned out my disks and never saw them again however Windows 3.1 had just come out with TT fonts so I was able to achieve similar results on my printer. The thing that killed Ensemble is the lack of support.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |