Hi Guys, Thanks for the quick response!
If I try to load SBINIT.COM before EMM386 I get the following error: "pci aduio driver requires emm386 or similar". Note: devload will not load SBINIT.COM in config.sys. "I think this means that the driver wants to get some RAM pages in the first page table, which maps the first 4 MB" I agree, but I also tried the below setting as suggested.... "DEVICE=C:\FDOS\BIN\HIMEMORY\EMM386 FRAME=NONE EMM=1024" ... and any /EMM=xxxx values below 2354 cause the following error: Illegal Instruction occurred CS=1FA7 IP=01FE SS=1FE5 SP=4D6C DS=0000 ES=1FCA EAX=0000DE0C EBX=00024BEA ECX=00010006 EDX=010037FC ESI=0001FE04 EDI=0100FE1A EBP=00014D74 OPCODES @CS:IP CD 67 9D 8B C1 1F 5F 5E ABORTING PROGRAM PCI AUDIO DRIVER NOT LOADING Illegal Instruction occurred CS=0357 IP=0030 SS=0BA6 SP=000C DS=0000 ES=025D EAX=00000700 EBX=00285E20 ECX=00000000 EDX=000037F0 ESI=00000493 EDI=0000C4E0 EBP=00003A48 OPCODES @CS:IP CD 67 84 E4 74 01 F9 FB ABORTING PROGRAM EMM386 - UNABLE TO CONTINUE - PLEASE REBOOT=yyyy ........(Note: yyyy= "running numbers") I have tried other memory managers like UMBPCI, but sbinit.com will not work with ones not having VCPI/DPMI. I get a error message indicating so when tring to load sbinit.com. If I sent you guys a soundblaster card and a DOS driver CD would you guys be willing to try and fix emm386 & himem64 to work with it? I would not need the card returned. Just let me know how & where you would like it sent. According to the driver info these Creative Labs DOS drivers will work with all but 2 of the cards that they currently have in production. If you don't mind me asking, what model DOS sound cards are you guys using that are currently available? I can always switch to another PCI audio card if it is going to be available for at least two or three years (and it dosen't cost a small fortune). The "one board wonders" with onboard sound using the 686A & 686B VIA southbridge controllers and BIOS blaster enabled are becoming scarce and not reliably available. This is what has caused me to resort to using a PCI audio card in the first place. I thank you all very much for your time and sincerely hope there is a solution for this problem soon. Best Regards, Brian __________________________________________________________________________________ From: Eric Auer <[EMAIL PROTECTED]> Re: EMM386 VCPI/DPMI Help / Question 2004-07-05 07:23 Hi! > >I just downloaded EMM386.EXE & HIMEM64.EXE from ftp.devoresoftware.com > >7/4/04, but I can"t seem to get them to work with the soundblaster > >SBINIT.COM driver which initializes my new soundblaster 16 PCI card. > > >"Could not allocate code/patch ram below 4mb boundary. > > DEVICE=C:\FDOS\BIN\HIMEMORY\EMM386 FRAME=NONE EMM=1024 I would like to add that some other programs simply have to be started BEFORE emm386. One such example is the Intel Plug and Play Manager for DOS / Windows 3. It initializes the ISA PnP and PCI busses (you usually only need that if your BIOS has no "PnP OS installed = no" setting around) and stays in RAM (quite small) to offer some services to Windows. Some EMM386 versions get confused by the 32 bit port I/O accesses. However, as those only happen during init (and during config changes / accesses with the enclosed tools or Windows), you can simply load the driver before EMM386 to solve the compatibility problem. Note that INSTALL lines are always processed after DEVICE lines, so because your SBINIT cannot be loaded as DEVICE, and because EMM386 can only be loaded as DEVICE (or does DEVLOAD work for it?), my suggestion will probably not solve YOUR problem. Anyway, Michael already suggested another solution :-). > >"Could not allocate code/patch ram below 4mb boundary. I think this means that the driver wants to get some RAM pages in the first page table, which maps the first 4 MB - normally, EMM386 will only fill the first 1 MB + HMA + some (some = for internal use of EMM386) at startup, and the rest will depend on EMS (and XMS) usage as far as I remember. During VCPI init, EMM386 tells the VCPI "client" which pages in the first 4 MB are already in use, maybe this is what the SBINIT error message is referring to? So other possible solutions MIGHT be (apart from NOEMS / FRAME=NONE) to exclude some areas from UMB area or EMS / XMS pool or allocate less than 4 MB from it or do allocations starting at the top of the memory (which can make things slow if you have an old motherboard and only the first 64 MB are cacheable area...). Would those ideas make any sense? Or am I completely messing up things here? Confusing greetings, Eric ;-). ************************************** ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
