Ok, I was born 1987. Had 386 and 486. Today I am software developer. I have cd in the tray. Tried to remove second hdd so it is on drive D and it does not help. Same use case is working in Windows 98 and its ms dos. So it is clearly some incompatibility in Freedos driver.
Please look at youtube, PhilsComputerLab. He has Youtube video about freedos gaming. He mentions exactly these issues and that he need to replace some files, but I dont know which files to replace. Thank you, Lukas On Tue 1. 6. 2021 at 19:57, Eric Auer <e.a...@jpberlin.de> wrote: > > Hi Lukas, > > > Please please I solved sound. I shared only experience. Please focus on > cd > > drive not found. Forget dosbox. I use original floppy discs from 1992. > Dont > > overcomplicate. Can u recommend which files replace from ms dos? > > Okay then. So there was no sound problem, you just used a DOSBOX > driver outside DOSBOX? If it is supposed to work with SB16 on real > hardware, supporting MS EMM386 style I/O traps would still be one > feature that I would like to see from Japheth in JEMMEX/JEMM386 :-) > > But you ask "please focus on CD drive not found". Then I ask: Please > tell me, do you have the CD in the drive? Can you access the files > on the CD? In other words, is only your game complaining, because it > does some copy protection check which has compatibility issues? Or > are you completely unable to access any files on the CD? Those are > two different problems which have two different solutions. Please > specify which versions of which drivers with which options you use. > > You also have not answered those questions: Out of which memory did > the installer run? Why have you used a Windows boot floppy instead > of the real FreeDOS installer boot floppy? As you have circumvented > the problem, you are free to ignore that question if you have no > time to tell me whether the installer would still fail if you use > it properly, but I am curious. > > I assume AWEUTIL /EM and Intel ICU for ISA PnP is what you have now > used to solve the MIDI sound problem, but it would be nice to know. > > Also, CTCM, CTSB16 and CTMMSYS are probably not perfect for AWE32: > > https://comp.sys.ibm.pc.games.rpg.narkive.com/duCiqd7H/ot-configuring-sb16-for-dos > But as long as it works for you, it is better to have a working than > to have an overly elegant solution. > > As you do NOT want too complicated answers, you should wait with > MSCLIENT and SAMBA attempts until you have the easy things fixed! > This means you should not load IFSHLP at the moment, I think. > > I also assume that the mouse works fine with CTMOUSE and that > your compact flash drive works great now? > > As nothing is known about the Terminator 2029 problem, you have > several remaining problems, but ALL relate to the same issue: > > Games which are not able to access the game CD. > > To solve that problem, you could start by answering my question > whether or not you can access files on the CD outside the game. > > For example, if the CD drive has letter D: then does DIR D: work > fine and show you a directory listing of the CD contents? Or is > there some error message? Which? Do you get error messages earlier > while booting, from UDVD2 or from SHSUCDX? What do those messages > say? You could also make screenshots if you prefer. You can press > F8 when DOS starts to boot: Then it will ask you for confirmation > for each line, which makes it easy to read or screenshot messages. > > >>> 3) Mass Destruction PC DOS game: installs from CD, fails to start. > >>> Tried both DOS4GW and DOS32A > >> > >> It says DOS/32A warning 9003: real mode vector has > >> been modified, and exits. > > According to http://dos32a.narechk.net/manual/html/user/8.htm > this is the fault of Mass Destruction itself, when it exits > without cleaning up vectors. Which leaves only the CD problem. > > Regards, Eric > > PS: This should be 123?DOS=HIGH and 23?DEVICE=...HIMEM... My > earlier comments about I=TEST, I=B000-B7FF NOVME and NOINVLPG > still apply. If games need EMS 3.2, you must also remove NOEMS > and you should not load IFSHLP until you have solved the rest. > > >> 12?DOS=HIGH > >> 12?DOS=UMB > >> 12?DOSDATA=UMB > >> 1?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST I=TEST NOVME NOINVLPG > >> 234?DEVICE=C:\FDOS\BIN\HIMEMX.EXE > >> 2?DEVICE=C:\FDOS\BIN\JEMM386.EXE X=TEST I=TEST I=B000-B7FF NOVME > NOINVLPG > >> 34?SHELL=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024 /P=C:\FDAUTO.BAT > >> 12?SHELLHIGH=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024 > /P=C:\FDAUTO.BAT > >> 123?DEVICE=C:\CTCM\CTCM.EXE > >> 123?DEVICE=C:\SB16\DRV\CTSB16.SYS /UNIT=0 /BLASTER=A:220 I:5 D:1 H:5 > >> 123?DEVICE=C:\SB16\DRV\CTMMSYS.SYS > >> 12?DEVICEHIGH=C:\NET\MSCLIENT\ifshlp.sys > > > > _______________________________________________ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user >
_______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
