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?
On Tue 1. 6. 2021 at 17:09, Eric Auer <e.a...@jpberlin.de> wrote: > > Hi Lukas, > > > Guys, I built regular 486DX2 66Mhz. I would not be that guy and put PCI > > soundcard in that machine. Of course I have ISA soundcard. I have even > VLB > > slot, but I use TSENG 4000/W32p for ISA. In PCI, there is only Realtek > NIC > > with XT-IDE EEPROM. > > Actually Realtek PCI Network cards and older PCI, AGP and PCIe graphics > cards work really well with DOS, but you made a good choice to use an > ISA soundcard for your old games on that 486DX2 PC. > > As said, your ISA soundcard is supposed to come with appropriate tools. > If it is SB16 compatible, games should be happy, but you may still have > to load some activation or volume control tool, set BLASTER and other > environment variables, maybe set jumpers. If the card is PnP, you may > have to install that large Intel DOS PnP manager thing. > > > A) 486DX2 66Mhz, 32MB Ram, onboard 256kB cache. BIOS does not allow CDROM > > boot, but combination of Windows98 floppy to boot and running > installation > > from FreeDOS cd works. At the end there it will crash due to out of > memory. > > Out of DOS memory or out of XMS, EMS or other memory? Those 32 MB > should certainly be enough for our installer, so the problem will > be something more specific than your overall size of RAM. > > Note that your install style is very non-standard, because the > installer has not been tested with MS DOS 7 (from your Windows > floppy). I recommend that you use a FreeDOS boot floppy instead, > or even better, our special boot floppy for the install CD :-) > > The CD installer may expect specific drivers to be loaded, while > your Win98 boot floppy may be using completely different drivers. > > http://freedos.org/download/ explicitly mentions the boot floppy > for those who want to use the CD without booting it. Sorry that > you had to spent 4 hours searching other workaround approaches. > > > said it is memory issue and solved also by installing FreeDOS on hard > drive > > in Pentium machine. That's how I did it as well and it works. Even > > installing a lot of packages on 486, the fdimples will crash with out of > > memory while browsing packages tree and selecting many packages. > > That sounds as if FDIMPLES had too little DOS memory free? Anyway, > while the solution to install your target harddisk into a PC which > CAN boot from CD is very nice, it does not really tell me which > solution would have worked for the 486 and whether it was really > the amount of memory. 32 MB sounds very okay. Maybe it was the > amount of DOS memory, because the Win98 floppy loaded too many > unnecessary drivers or something like that? > > > B) I have Realtek original DOS packet driver, default interrupt 0x60. No > > problem with that. Just documentation for MTCP tells me to install FDNET > > Ah okay. I think if you have the Realtek (8139 or similar, I guess) > packet driver anyway, you only have to complete some config settings > for mTCP and the packet driver. No need to install extra components > as far as I know. Ask Michael Brutman (e.g. here) for config hints :-) > > > C) I have Sound Blaster AWE 32 and AWE 64. > > The AWE 32 is pretty cool for DOS games! I remember that it came > with a volume control tool and a setup-at-boot tool and that it > was recommended to install the intel plug and play configuration > utility: https://drivers.dosreloaded.de/Plug&Play/Intel%20ICU/ > > > I have sound + cdrom + network (including Samba support) with dhcp + > > mouse + compact flash working. Everything is working on this side. > > Sound should be relatively easy. For CDROM, use the three drivers > which I have recommended. You may replace UDVD2 by whatever came > with your CD/DVD drive, but UDVD2 probably works better. > > Networking with Samba is a bit complicated to configure, but Bryan > and Frantisek have recently done that for Bryan's computers, so > they can probably share some tricks. > > Mouse (PS/2 or RS232) should be easy, too: Use CTMOUSE. If you have > USB mice, modern BIOS will have some legacy support which translates > it to a simulation of PS/2 which you can use in CTMOUSE. If you have > an old BIOS, you can try Bret Johnson's USB drivers. > > Not sure what you mean by compact flash, do you mean a card reader > or do you mean a purely mechanical adapter to connect CF to your > IDE/ATA connectors on the mainboard? The latter should work without > any drivers, but you cannot change "disks" while DOS is running and > you may have to be careful to use proper geometry and partitioning. > > > some games install from CD and won't run because they complain cannot > find > > CD. Mostly computer will seek floppy drive A: when searching for CD. I > > guess it is some kind of copy protection. > > No idea, but I assume you do have CD drivers loaded and working in > general? In that case it would be interesting to know whether there > is indeed a copy protection using exotic functions which differ in > how SHSUCDX and UDVD2 differ from MSCDEX and ancient CD-ROM drivers? > > > So making ISO image will not work unless you... > > I would not be too sure about that. Simple copy protections might > already be happy with finding the "actual" CD as CD or ISO, while > just being unhappy when the game is on a directory on harddisk? > Which games are affected? > > > I have uploaded FDAuto.bat and FDConfig.sys together with screenshots > > OneDrive here (you have permission to update it directly): > > https://1drv.ms/u/s!Aq5X0D4OWWAThYBsnQ0sI1_Me83H5g?e=Nsstqv > > Let me copy paste the configs below :-) You can simplify the config > a lot if you lock it to 386+ instead of keeping the automated CPU > type based different configs. Should I give an example? The quote > omits some comments from your file. I see you have already added > the Sound Blaster AWE 32 tools yourself, nice. Does the SB AWE32 > work in most games now? Where does it work, where not? > > I recommend that you remove the I=TEST and I=B000-B7FF options. > > You can probably also remove the NOVME and NOINVLPG options, as > those are only required in certain buggy PC emulator versions. > > Also, I recommend that you use boot option 2 or 3 for everyday use. > > > 1) [OPTIONAL] SoftMPU crash JEMMEX Exception 06 > > The SOFTMPU 1.91 message says it is from DOSBOX. Why > would you use that version, when your SB AWE32 has > real MIDI hardware? The exception 06 is undefined > opcode according to this: > > https://sandpile.org/x86/except.htm > > The code is F0 12 etc. which is a bad lock prefix, > but jumping to 0000:0017 probably is a bug in itself. > Maybe it tried to do something which only DOSBOX can. > > > 2) Tried SoftMPU boot without both JEMMEX and JEMM386 > > Now THAT is interesting! It requires EMM386 4.46 or > QEMM 7.03 or newer. Which means that it tries to use > protected mode I/O port trapping to simulate MIDI on > systems where no hardware MIDI exists. > > You do not need SOFTMPU for SB AWE32 at all :-) But > you can check the JEMMEX or JEMM386 documentation to > read about special SB Live or SB PCI compatibility > options where similar tricks as in SOFTMPU are used, > or you could use MS EMM386. Again, I think the better > option is to not use SOFTMPU. > > You can use the AWEUTIL /EM options for your SB AWE32 :-) > > Read the docs, the full answer might be a bit more > complex, but in any case, the AWE drivers have what > you need while SOFTMPU is not the right choice here. > > > 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. You could try loading > CWSDPMI or DPMIONE in resident mode before loading > massd, to bypass the complaining part of DOS/32A? > > > 4) Destruction Derby: install from CD, fail to start > > It says No CD in drive. Is there a CD in your drive? > Can you access the files on the CD without problems? > > > 5) Comanche Gold CD: install, fail to start > > Basically same question as in 4) > > > 6) Terminator 2029: installation from floppy drive will throw some > JEMM386 > > error. Booting without it does not help. > > Now it says exception 06 at 125c:136 again with > a bad lock prefix (f0 60 00 00 f0 60 00 00) which > makes me think that it may have jumped into some > data instead of a code location. What happens in > the case where you load JEMM386 instead, or where > you load neither, just HIMEM? > > > 7) Booting to FreeDOS without memory manager does not help with > Terminator > > 2029 either. Installation is from floppy drive. Game is from 1992 and > > requirements are 286 w/640k, 1MB Expanded Memory. > > It says invalid opcode at 013c 1221 0293 4b4f 00ff > 0000 fd00 7f20 009f f09a 1dfe 5150 but you say it > needs expanded memory. You have HIMEMX 3.35 loaded > and it uses Keyboard Controller style A20 control. > Have you tried XMGR instead? Available e.g. here: > > http://mercurycoding.com/downloads.html#DOS > > You could also try WITH jemm386 or jemmex, or you > could try the HIMEMX command line options which let > you select different A20 control styles. Some old > games also act confused if you have too much RAM, > so HIMEMX has options to hide some of the RAM :-) > > Regards, Eric > > > > *FDCONFIG.SYS* > > SET DOSDIR=C:\FDOS > > !COUNTRY=001,858,C:\FDOS\BIN\COUNTRY.SYS > !LASTDRIVE=Z > !BUFFERS=20 > !FILES=40 > !MENUCOLOR=7,0 > > MENUDEFAULT=1,5 > MENU 1 - Load FreeDOS with JEMMEX, no EMS (most UMBs), max RAM free > MENU 2 - Load FreeDOS with JEMM386 (Expanded Memory) > MENU 3 - Load FreeDOS low with some drivers (Safe Mode) > MENU 4 - Load FreeDOS without drivers (Emergency Mode) > > 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 > > *FDAUTO.BAT* > > @ECHO OFF > > set DOSDIR=C:\FDOS > > set LANG=EN > > set TZ=UTC > > set PATH=%dosdir%\BIN > > if exist %dosdir%\LINKS\NUL set PATH=%path%;%dosdir%\LINKS > > set NLSPATH=%dosdir%\NLS > > set HELPPATH=%dosdir%\HELP > > set TEMP=%dosdir%\TEMP > > set TMP=%TEMP% > > SET CTCM=C:\CTCM > > SET SOUND=C:\SB16 > > SET BLASTER=A220 I5 D1 H5 P330 E620 T6 > > SET MIDI=SYNTH:0 MAP:E MODE:0 > > set DIRCMD=/P /OGN /Y > > set COPYCMD=/-Y > > set OS_NAME=FreeDOS > > set OS_VERSION=1.3-RC4 > > set autofile=C:\FDAUTO.BAT > > set cfgfile=C:\FDCONFIG.SYS > > alias cfg=edit %cfgfile% > > alias auto=edit %autofile% > > alias reboot=fdapm warmboot > > alias reset=fdisk /reboot > > alias halt=fdapm poweroff > > alias shutdown=fdapm poweroff > > > > if not exist %dosdir%\bin\vinfo.com goto Only8086 > > vinfo /m > > if errorlevel 3 goto Support386 > > if errorlevel 2 goto Support286 > > > > :Only8086 > > if "%config%"=="2" goto END > > MEM /C /N > > goto FINAL > > > > :Support286 > > if "%config%"=="3" goto END > > LH FDAPM APMDOS > > CTMOUSE > > MEM /C /N > > goto FINAL > > > > :Support386 > > if "%config%"=="4" goto END > > > > LH FDAPM APMDOS > > CTMOUSE > > > > SHSUCDX /QQ /D3 > > REM LH SHSUCDHD /QQ /F:FDBOOTCD.ISO > > DEVLOAD /H /Q %dosdir%\BIN\UDVD2.SYS /D:FDCD0001 > > SHSUCDX /QQ /~ /D:?SHSU-CDR,D /D:?SHSU-CDH,D /D:?FDCD0001,D > /D:?FDCD0002,D /D:?FDCD0003,D > > > > MEM /C /N > > SHSUCDX /D > > > > C:\CTCM\CTCU /S > > C:\SB16\DIAGNOSE /S > > C:\SB16\AWEUTIL /S /R:30 /C:30 > > C:\SB16\SB16SET /P /Q > > > > :FINAL > > if not exist %dosdir%\bin\fdnet.bat goto NoNetwork > > C:\DRIVERS\RTSPKT.COM 0x60 > > call %dosdir%\bin\fdnet.bat start > > if errorlevel 1 goto NoNetwork > > > > :NoNetwork > > if exist %dosdir%\bin\fdassist.bat call %dosdir%\bin\fdassist.bat > > > if exist %dosdir%\bin\welcome.bat call %dosdir%\bin\welcome.bat > > > > :END > > > > _______________________________________________ > 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
