Re: [Freedos-user] Sound Blaster 16 issues...
Hi, On Tue, Oct 4, 2011 at 10:09 PM, John Ames commodorej...@gmail.com wrote: From: Rugxulo rugx...@gmail.com Subject: Re: [Freedos-user] Sound Blaster 16 issues... Are you running latest FreeDOS kernel and HIMEMX + JEMM386? (Somehow I doubt it.) Try upgrading a few of your system files and try again. Else try booting a somewhat cleaner config without a lot of extra TSRs and drivers. You'll have to give more details, though, for further guesses. That helped; I updated the kernel and installed JEMMEX in place of HIMEM.EXE and EMM386.EXE. CTSB16.SYS now loads without issue. SBCD.SYS still crashes, however; JEMM seems to be catching some kind of protection fault. Here's the output, now that it politely prints one message instead of perpetually scrolling up the screen ;) Try JEMMEX X=TEST I=TEST since by default I think it's less careful than it perhaps could be regarding UMBs. Or even read the docs and try the ultra super safe option. Hmmm, lemme find and quote it (for convenience): X=A000- NOHI NOVME NOINVLPG (if that doesn't work, nothing will). BTW, this is a naive question, but do you really need EMS? If not, avoid JEMM386 altogether and just load HIMEMX (or XMGR or FDXMS or similar). It may avoid some rare problems (including this one, though I halfway doubt it without trying it). And if you also really need UMBs, you could try UMBPCI, but I doubt that would fix anything. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Sound Blaster 16 issues...
Hi, Are you running latest FreeDOS kernel and HIMEMX + JEMM386? (Somehow I doubt it.) Try upgrading a few of your system files and try again. Else try booting a somewhat cleaner config without a lot of extra TSRs and drivers. You'll have to give more details, though, for further guesses. http://www.freedos.org/software/?prog=kernel http://www.freedos.org/software/?prog=himemx http://www.freedos.org/software/?prog=jemm386 On Mon, Oct 3, 2011 at 5:49 PM, John Ames commodorej...@gmail.com wrote: I've got an ISA SB16 on a 486 box I've installed FreeDOS on. I had trouble installing the driver software to begin with, as the installer didn't want to run until I booted into MS-DOS 6.22. Now it's installed, enough that games can recognize and use the hardware. However, I'm still running into some trouble with it. CTSB16.SYS and SBCD.SYS both have DEVICE lines in FDCONFIG.SYS, which I copied over from the CONFIG.SYS created by the installer, as does CTMMSYS.SYS. However, while CTMMSYS works without issue, CTSB16 and SBCD both crash during boot. This is a bit of a problem, as without these I can't use the companion CD-ROM drive (and I don't have an IDE controller capable of driving a newer CD-ROM on hand.) SBCD gives me Invalid Opcode error messages, like some of the other utilities did until I ran them under MS-DOS. CTSB16, on the other hand, goes insane and prints screenfuls of gibberish. I've got them both commented out for now, but that still leaves me with no CD access. Does anybody have any idea what, if anything, can be done to get these working on FreeDOS? Or should I just settle for finding a separate CD-ROM drive and controller? -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Sound Blaster 16 issues...
Hi, On Sun, Oct 2, 2011 at 3:24 PM, Michael C. Robinson plu...@robinson-west.com wrote: A Soundblaster is the industry standard card. You mean was. :-( To say modern soundcards are incompatible is an understatement. Your only hope is really old hardware or emulators (DOSBox, QEMU, maybe DOSEMU). If you have a 100% true Soundblaster 16, freedos can use it. I successfully tricked Windows 98SE dos drivers for a PCI soundblaster 16 to work in Freedos. There should be an open source replacement driver for the soundblaster 16 cards, but I don't know how similar these cards really are. I hope an OSS driver is part of freedos 1.1. The only two people offhand that I think?? know anything about soundcards are Michael Kostylev and Atila Padar. The former allegedly ported OSS to DOS at one time for Mplayer (but he's not active anymore). Also, Atila is the Mpxplay dude who has ported bits of ALSA for his program. Very imcomplete, but at least having proof that somebody can do it is hopeful, right? But anyways, my real point is that (as Pat V. had mentioned months ago) we should probably focus on importing drivers from another OS, e.g. FreeBSD. I think there have been several attempts in the past at making such portable drivers, but I don't know how useful they would be to us. (If I wasn't such a noob, I'd try myself, but that's way way way beyond me.) I mention the following URLs here just for reference on the odd chance that it helps somebody somewhere: http://code.google.com/p/rosetta-os/w/list http://www.projectudi.org/ -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Sound Blaster 16 issues...
В ответ на сообщение товарища John Ames, датированное 3-Oct-2011 17:49: I've got an ISA SB16 on a 486 box I've installed FreeDOS on. I had My congratulations! :-) However, while CTMMSYS works without issue, CTSB16 and SBCD both crash during boot. Below I will share my small experience. I do not have troubles with following setings. fdconfig.sys DEVICEHIGH=D:\DRV\AWE64\DRV\CTSB16.SYS /UNIT=0 /BLASTER=A:220 I:5 D:1 H:5 DEVICEHIGH=D:\DRV\AWE64\DRV\CTMMSYS.SYS fdauto.bat SET BLASTER=A220 I5 D1 H5 P330 E620 T6 SET SOUND=D:\DRV\awe64 SET CTCM=D:\DRV\awe64\ctcm.exe SET MIDI=SYNTH:1 MAP:E D:\DRV\awe64\ctcm.exe D:\DRV\awe64\aweutil.com /s D:\DRV\awe64\mixerset /p /q -- bloger -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Sound Blaster 16 issues...
Hi John, I've got an ISA SB16 on a 486 box I've installed FreeDOS on. Very old hardware :-) installed, enough that games can recognize and use the hardware. Very nice. Only true ISA soundcards really please old games. However, I'm still running into some trouble with it. CTSB16.SYS and SBCD.SYS both have DEVICE lines in FDCONFIG.SYS, which I copied over I do not think that you really need those or CTMMSYS for anything today. This is a bit of a problem, as without these I can't use the companion CD-ROM drive (and I don't have an IDE controller capable of driving a newer CD-ROM on hand.) SBCD gives me Invalid Opcode error messages, like some of the other utilities did until I ran them under MS-DOS. That is odd... ATAPI CDROM should be very similar to any IDE as far as I remember, so I am not sure whether it is truly not possible to run them on your old main IDE controller... Of course soundcard CDROM tended to so somewhat incompatible so I would not expect those to run with any other controller. leaves me with no CD access. Hard to tell what goes wrong with your SBCD driver. I guess you would just load that - possibly with some options when it has no autodetection of right settings - and then SHSUCDX (the MSCDEX replacement). Maybe there are some issues with other drivers loaded at the same time - try without EMM386. Regards, Eric -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Sound Blaster 16 issues...
At 11:53 AM 10/4/2011, Eric Auer wrote: This is a bit of a problem, as without these I can't use the companion CD-ROM drive (and I don't have an IDE controller capable of driving a newer CD-ROM on hand.) SBCD gives me Invalid Opcode error messages, like some of the other utilities did until I ran them under MS-DOS. That is odd... ATAPI CDROM should be very similar to any IDE as far as I remember, so I am not sure whether it is truly not possible to run them on your old main IDE controller... There where a few non-ATAPI CD-ROM drives around back then with the interface simply not compatible. Don't know the details after more than 15 years, but it had to do with the controller chips (either there was one on the SB card that didn't go along with the one on the drive or the other way around). There were also some SB cards that in fact had SCSI controllers on them, for use with SCSI based CD-ROM drives only. I used to have one of those back at the company I was employed at from '85-'94, actually 'borrowing' a SCSI CD-ROM drive from a Sun Pizzabox... Ralf -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Sound Blaster 16 issues...
From: Rugxulo rugx...@gmail.com Subject: Re: [Freedos-user] Sound Blaster 16 issues... Hi, Are you running latest FreeDOS kernel and HIMEMX + JEMM386? (Somehow I doubt it.) Try upgrading a few of your system files and try again. Else try booting a somewhat cleaner config without a lot of extra TSRs and drivers. You'll have to give more details, though, for further guesses. That helped; I updated the kernel and installed JEMMEX in place of HIMEM.EXE and EMM386.EXE. CTSB16.SYS now loads without issue. SBCD.SYS still crashes, however; JEMM seems to be catching some kind of protection fault. Here's the output, now that it politely prints one message instead of perpetually scrolling up the screen ;) JemmEx: exception 0D occured at CS:EIP=09DE:0001, ERRC= SS:ESP=09DE:2CE8 EBP=F8002D02 EFL=00033286 CR0=8013 CR2= EAX= EBX=99FF ECX= EDX=09DE ESI=01709087 EDI=000A9087 DS=9DC6 ES=9DC6 FS=C81F GS=09DE [CS:IP]=00 00 00 00 00 00 00 00 Press ESC to abort program It goes on to produce an indefinite number of further errors, the only difference being that EFL increments by random amounts and [CS:IP] now contains FF FF FF FF 00 C8 51 11. Not sure what all of that is relevant, but unless someone can tell me how to get a core dump in the middle of the boot process, that's all I can offer at the moment. From: Eric Auer e.a...@jpberlin.de Subject: Re: [Freedos-user] Sound Blaster 16 issues... That is odd... ATAPI CDROM should be very similar to any IDE as far as I remember, so I am not sure whether it is truly not possible to run them on your old main IDE controller... Of course soundcard CDROM tended to so somewhat incompatible so I would not expect those to run with any other controller. Yeah, that's the problem. According to everything I've read, it's not a standard IDE interface, it only works with SB16. I could just track down a separate controller and a newer CD-ROM, I suppose, but I'd prefer to work with what I have for the moment. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Sound Blaster 16 issues...
A Soundblaster is the industry standard card. If you have a 100% true Soundblaster 16, freedos can use it. I successfully tricked Windows 98SE dos drivers for a PCI soundblaster 16 to work in Freedos. There should be an open source replacement driver for the soundblaster 16 cards, but I don't know how similar these cards really are. I hope an OSS driver is part of freedos 1.1. On Mon, 2011-10-03 at 17:49 -0500, John Ames wrote: I've got an ISA SB16 on a 486 box I've installed FreeDOS on. I had trouble installing the driver software to begin with, as the installer didn't want to run until I booted into MS-DOS 6.22. Now it's installed, enough that games can recognize and use the hardware. However, I'm still running into some trouble with it. CTSB16.SYS and SBCD.SYS both have DEVICE lines in FDCONFIG.SYS, which I copied over from the CONFIG.SYS created by the installer, as does CTMMSYS.SYS. However, while CTMMSYS works without issue, CTSB16 and SBCD both crash during boot. This is a bit of a problem, as without these I can't use the companion CD-ROM drive (and I don't have an IDE controller capable of driving a newer CD-ROM on hand.) SBCD gives me Invalid Opcode error messages, like some of the other utilities did until I ran them under MS-DOS. CTSB16, on the other hand, goes insane and prints screenfuls of gibberish. I've got them both commented out for now, but that still leaves me with no CD access. Does anybody have any idea what, if anything, can be done to get these working on FreeDOS? Or should I just settle for finding a separate CD-ROM drive and controller? -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Sound Blaster 16 issues...
I've got an ISA SB16 on a 486 box I've installed FreeDOS on. I had trouble installing the driver software to begin with, as the installer didn't want to run until I booted into MS-DOS 6.22. Now it's installed, enough that games can recognize and use the hardware. However, I'm still running into some trouble with it. CTSB16.SYS and SBCD.SYS both have DEVICE lines in FDCONFIG.SYS, which I copied over from the CONFIG.SYS created by the installer, as does CTMMSYS.SYS. However, while CTMMSYS works without issue, CTSB16 and SBCD both crash during boot. This is a bit of a problem, as without these I can't use the companion CD-ROM drive (and I don't have an IDE controller capable of driving a newer CD-ROM on hand.) SBCD gives me Invalid Opcode error messages, like some of the other utilities did until I ran them under MS-DOS. CTSB16, on the other hand, goes insane and prints screenfuls of gibberish. I've got them both commented out for now, but that still leaves me with no CD access. Does anybody have any idea what, if anything, can be done to get these working on FreeDOS? Or should I just settle for finding a separate CD-ROM drive and controller? -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
