 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Forum / Windows 98 / General Topics / May 2008EMM386: Unrecoverable privileged operation error #I7
Inside Win98SE's "pure DOS", when I run the DOS utility called "nvram120.exe", I see the subject line error on screen, and then I have to reboot. (I wanted to run this utility to see if I could see if a particular ISA card was installed correctly.) My mobo is Supermicro P6SBU revision 1.01, and I have flashed the BIOS to revision 3.1 (latest). The BIOS is called American Megatrends AMIBIOS setup, version 2.5 (c) 1997. When I was setting up the mobo (yesterday), I was encountering the following situations: 1) After installing my PCI cards (one at a time), I noticed that the BIOS appeared to be "forgetting" some of these cards in the POST device listing section. (In other words, some cards were being ommitted from the device listing on reboot.) 2) I also noticed that the "Checking NVRAM..." BIOS POST message kept saying "...Update OK!", even though between some reboots I had installed no additional hardware. 3) I also noticed that sometimes a PCI card would be listed as "Unknown Device", but if I moved the card to a different slot, it would then be correctly identified as (for instance) "Multimedia Device". 4) I have also encountered a BSOD when I installed a Diamond 3dfx card in one particular PCI slot, but then this BSOD would not occur if I moved the card to a different slot. (Also, this "bad slot" in question didn't seem to be a bad slot, as I tested it with another PCI card and it seemed ok.) To address some of the issues above, in Windows98SE I decided to Disable NVRAM/ESCD updates inside Plug and Play BIOS properties inside System/Device Manager. This appeared to fix the perpetual Checking NVRAM...Update OK! message on every reboot, and also appeared to fix one or two other resource conflict problems, but not the subject line problem. Regarding the BIOS (as described at the top of this message), I've never seen so many options you can adjust. I'm sure somewhere buried in these options is a "fix" for every problem I'm likely to stumble in to, but it's a technical minefield, because I've never used this mobo before. I tried loading in the BIOS Fail-Safe options to try and fix the subject line problem, but that didn't work. ATM, I have this hardware (which all seems to work) - 3 ISA slots = all completely empty now. There *was* a legacy SB16 which worked perfectly, but I removed it to test a legacy Gravis UltraSound which didn't work, and so it was removed as well. AGP slot = Matrox graphics card G450 PCI slot 1 (a shared slot with an ISA slot) = empty. (This seemed to be a bit of a problematic slot, so I've left it empty for now.) PCI slot 2 = 3dfx card. Was causing BSOD on install, but now seems fine. PCI slot 3 = Matrox graphics card G200 (for connecting to above 3dfx card). Works fine within a "Win98SE hardware configuration profile" so that I can toggle between this PCI graphics card, and the AGP graphics card listed above. PCI slot 4 = Creative PCIAudio ES1371 sound card. Works fine. Phew, that's it I think. Sorry for the long post! Thanks for any suggestions at all. Best regards, Robert. > Inside Win98SE's "pure DOS", when I run the DOS utility called > "nvram120.exe", I see the subject line error on screen, and then I [quoted text clipped - 27 lines] > question didn't seem to be a bad slot, as I tested it with another PCI > card and it seemed ok.) This is fairly common. Check to see if the bios has an option to set the pci resources to AUTO. (some have both manual and AUTO options.) Also see if you can find the manual for the mobo. If it has an AGP slot, there are a few mobo's out there where you cannot use the PCI slot next to it if there is an AGP card in use.(Just to list one of many possible idiosyncrasies.) But basically, if a card does not work in one slot, but works OK in another... simply leave it that way. No sense in trying to force a configuration that is just plain unworkable. > To address some of the issues above, in Windows98SE I decided to > Disable NVRAM/ESCD updates inside Plug and Play BIOS properties inside [quoted text clipped - 33 lines] > Phew, that's it I think. Sorry for the long post! Thanks for any > suggestions at all. Best regards, Robert. To add to the above, Brian provided a link to emm386 information in the old thread. The PCI/ISA slot you reference is an *either* slot, pick which one you want to use as the IRQ/addressing is shared, the same as Philo mentions sometimes occurs with the AGP and first PCI slot [depends upon the board - might also want to check to see if the BIOS has a specific setting for the slot; like assign IRQ, or other.... SOMETIMES you can stick another card {non-video} in the slot and Windows will recognize it as not in conflict {though you may need to manually assign the IRQ and addressing}. Also check whether you have enabled side-band addressing, wait a minute,,, what version of AGP is it? If its the early 2 version [not 1.0 which really wasn't AGP at all; VERY few cards actually functioned properly with it], many of those had difficulty as they failed to fully or properly implement the standard. AMI had two diagnostic tools available, one called AMI Setup [which was a full blown test tool], and another called AMITEST [basic diagnostics]. See if you can find those old versions somewhere. IF you continue to get BIOS errors which you described, first try those AMI tools, then you may need to re-flash the BIOS [sometimes it took twice to get it to *take*,, BTW, did you tell the flasher to replace the boot block?  SignatureMEB http://peoplescounsel.orgfree.com -- _________ | > Inside Win98SE's "pure DOS", when I run the DOS utility called | > "nvram120.exe", I see the subject line error on screen, and then I [quoted text clipped - 78 lines] | > Phew, that's it I think. Sorry for the long post! Thanks for any | > suggestions at all. Best regards, Robert. >Inside Win98SE's "pure DOS", when I run the DOS utility called >"nvram120.exe", I see the subject line error on screen, and then I >have to reboot. (I wanted to run this utility to see if I could see >if a particular ISA card was installed correctly.) You may like to try running nvram120 from real DOS with no memory manager loaded. You could also try the following utility: http://www.users.on.net/~fzabkar/BIOSutil/Phoenix/pnpbtst7.exe >My mobo is Supermicro P6SBU revision 1.01, and I have flashed the BIOS >to revision 3.1 (latest). The BIOS is called American Megatrends >AMIBIOS setup, version 2.5 (c) 1997. <snip> >2) I also noticed that the "Checking NVRAM..." BIOS POST message kept >saying "...Update OK!", even though between some reboots I had >installed no additional hardware. That's because Windows re-enumerates your hardware and updates the ESCD table in the NVRAM area of your BIOS chip. On a subsequent reboot the BIOS undoes the changes made by Windows. >To address some of the issues above, in Windows98SE I decided to >Disable NVRAM/ESCD updates inside Plug and Play BIOS properties inside [quoted text clipped - 9 lines] >before. I tried loading in the BIOS Fail-Safe options to try and fix >the subject line problem, but that didn't work. Here is a dump of *all* your BIOS options, including the hidden ones: http://www.users.on.net/~fzabkar/SuperMicro/SBUB21.RPT This was the BIOS image that I used (version R3.1): http://www.supermicro.com/support/bios/BIOS_ZIP/sbub21.zip Here is AMI's BIOS configuration utility: http://www.users.on.net/~fzabkar/SuperMicro/BCP760.EXE - Franc Zabkar SignaturePlease remove one 'i' from my address when replying by email. <snipped previous post messages to simplify things a bit> Franc, please may I ask you a somewhat off-topic question? Many thanks if this is OK... It's regarding a used MSI motherboard I bought recently. The model is: MS6119 ver 1.2 BX2 If I attach a large capacity HDD to this mobo (such as a 160gb or 300gb HDD), it hangs on POST when the mobo attempts to ascertain it's size. If I physically "cap" the HDD with a jumper to limit its size to 32gb, everything is OK. I flashed the BIOS to the very latest version (version p2.9, Award) and I also tried flashing to the penultimate version as well (version p2.8, Award). URL information = http://global.msi.com.tw/index.php?func=downloaddetail&type=bios&maincat_no=1&pr od_no=332 Browsing this MSI website, I notice with interest that they have two different BIOSs on offer for the same board - one is a more up-to-date Award BIOS (which I have tried as mentioned above), the other is an older dated AMI BIOS. (Please note, I haven't tried the older AMI BIOS offerings yet.) I *think* (regarding large capacity HDDs) that I may be out of luck with this mobo, but before I give up on it, I'd thought I'd run this problem past you to see if you could offer any pearls of wisdom. Many thanks, best regards, Robert. > <snipped previous post messages to simplify things a bit> > [quoted text clipped - 30 lines] > > Many thanks, best regards, Robert. Robert: The "s6119s2a.exe" file listed on this page: http://global.msi.com.tw/index.php?func=downloaddetail&type=bios&maincat_no=1&pr od_no=332 says it supports drives larger than 64Gig Also on the above page is a listing for the p2.9 BIOS where it states: "This is only for mainboard with "CPU PLUG AND PLAY" function." Perhaps your MB does not have this function and cannot use the p2.9 BIOS. HTH & GL John Signature\\\||/// ------------------o000----(o)(o)----000o---------------- ----------------------------()-------------------------- '' Madness takes its toll - Please have exact change. '' John Dulak - Gnomeway Services - http://tinyurl.com/2qs6o6 > The "s6119s2a.exe" file listed on this page: > [quoted text clipped - 9 lines] > > John Hi John, Many thanks for your post. I must admit that I previously spent over half an hour trying to get my head around this BIOS webpage from MSI. The thing is, my 6119 mobo is a CPU PnP mobo. And so I tried both the p2.8 and p2.9 PnP BIOSs, but they both hung with a large HDD attached. Now it's so interesting that they also list a "special" BIOS on this webpage, as you pointed out, which deals with large HDDs. But, the problem I have is that it states this particular BIOS (Version s2.a) is for the standard (non-PnP) mobo. Now my reasoning says "don't use it, you've got the PnP mobo and not the standard mobo". But should I give it a go?!?! Best regards, Robert. >> The "s6119s2a.exe" file listed on this page: >> [quoted text clipped - 28 lines] > > Best regards, Robert. Robert: It is a bit ambiguous. If it were mine and I did not have a lot invested in it, I would try it. If it is flat out WRONG the flash utility will probably give an error message if you try. Even if it fails to solve your problem there is a fighting chance you can revert to the old BIOS and be no worse off than you are now. YMMV John Signature\\\||/// ------------------o000----(o)(o)----000o---------------- ----------------------------()-------------------------- '' Madness takes its toll - Please have exact change. '' John Dulak - Gnomeway Services - http://tinyurl.com/2qs6o6 >Hi John, > [quoted text clipped - 14 lines] > >Best regards, Robert. I would think that a PnP motherboard first detects the CPU type via a BIOS CPUID routine, then looks up a Vcore table, and finally applies the correct voltage to the CPU. Or maybe the Vcore can be manually set in the BIOS setup, in which case the BIOS would consult the appropriate location in CMOS RAM and then set Vcore accordingly. A non-PnP BIOS would expect that the Vcore would be hardwired via jumpers, which means that the BIOS could not control the Vcore. Hence the Vcore voltage would remain at whatever level it initially powered up at. I would think that this initial level would be the maximum possible Vcore because otherwise you would not be able to power up those CPUs requiring the highest voltages. It is only when the BIOS determines that the CPU is a lower voltage type that the Vcore voltage can be programmatically reduced. However a non-PnP BIOS would not be able to do this, so the Vcore would remain at maximum, possibly destroying the CPU (???). That's my theory anyway ... - Franc Zabkar SignaturePlease remove one 'i' from my address when replying by email. >>Hi John, >> [quoted text clipped - 35 lines] > >- Franc Zabkar I just realised your board supports Pentium II and III CPUs. These use VID pins for setting the voltage. AFAICT this means that the CPU itself can correctly configure its Vcore voltage without external assistance. Whether your board does it this way, I don't know. - Franc Zabkar SignaturePlease remove one 'i' from my address when replying by email. >It's regarding a used MSI motherboard I bought recently. The model >is: [quoted text clipped - 5 lines] >size. If I physically "cap" the HDD with a jumper to limit its size >to 32gb, everything is OK. This person has done a lot of patching to BIOSes of that era: http://web.inter.nl.net/hcc/J.Steunebrink/k6plus.htm It appears that these BIOSes were limited to 128GB HDs. The OP in this thread appears to have the same problem as you: http://www.wimsbios.com/phpBB2/topic1278.html "Rainbow" claims he "can patch the 64GB bug in v2.9 BIOS". This is his/her list of patched BIOSes (limited to 128GB): http://wims.rainbow-software.org/index.php?count=-1 "The 32GB bug in Award BIOS that prevents many users from using HDD larger than 32GB (BIOS hangs at detection) can be easily fixed in existing BIOSes. The 64GB bug that causes hang at configuration table can be also fixed." >I flashed the BIOS to the very latest version (version p2.9, Award) >and I also tried flashing to the penultimate version as well (version [quoted text clipped - 15 lines] > >Many thanks, best regards, Robert. The following links may be useful. Harddisk Upgrade: The BIOS IDE Harddisk Limitations: http://web.inter.nl.net/hcc/J.Steunebrink/bioslim.htm BIOS Int 13h Extensions detection utility (6 KB ZIP-file): http://web.inter.nl.net/hcc/J.Steunebrink/extbio13.zip - Franc Zabkar SignaturePlease remove one 'i' from my address when replying by email. <I snipped everything here, because I'm worried it will mess up OE readers> > This person has done a lot of patching to BIOSes of that era:http://web.inter.nl.net/hcc/J.Steunebrink/k6plus.htm > [quoted text clipped - 18 lines] > > - Franc Zabkar Oh wow! I've got some homework to do! ;-) After reading all of the articles (amazing research Franc, thanks so much!), your observation that "It appears that these BIOSes <for MSI mobo version MS6119> were limited to 128GB HDs." is absolutely spot-on correct. It's a terrible shame that I've already invested in three brand new 300gb drives for my three legacy PC boxes, and as such I feel as if I ought to keep the drives and move on to a different mobo. The mobo was very cheap, plus it came with a CPU and stick of RAM, both of which I'm already using for something else, so there's not much lost here. Plus this problem came to light immediately when I first tried to use the mobo, so the amount of time lost was very small as well. Thanks very much for everyone's interesting comments! Best regards, Robert. >your observation that "It appears that these BIOSes <for MSI >mobo version MS6119> were limited to 128GB HDs." is absolutely spot-on [quoted text clipped - 3 lines] >300gb drives for my three legacy PC boxes, and as such I feel as if I >ought to keep the drives and move on to a different mobo. I have a socket 7 motherboard of the same era. Its AMI BIOS is limited to 128GB HDs. However, I know of one individual with the same motherboard who says he is running "a pair of 400 GB drives and a 500 GB drive, all with overlays". He is using W2K, though. - Franc Zabkar SignaturePlease remove one 'i' from my address when replying by email. > >your observation that "It appears that these BIOSes <for MSI > >mobo version MS6119> were limited to 128GB HDs." is absolutely spot-on [quoted text clipped - 12 lines] > -- > Please remove one 'i' from my address when replying by email. I think that's the key to this situation: overlays. However, just for the time being, I want to avoid them and try and find a mobo that will simply not hang on POST and allow me access to approx 137gb of my 300gb HDDs space. After I get a lot of things working etc, I can then look again at trying to get the mobos to get access to the rest of the HDDs space somehow. (Although if I couldn't achieve this, it wouldn't be a "show-stopped".) Thanks a lot, best regards, Robert. > <snipped previous post messages to simplify things a bit> > [quoted text clipped - 30 lines] > > Many thanks, best regards, Robert. also > "But should I give it a go?!?!" Beware! You may /kill/ the motherboard. I did with the reverse process. I was unable to find what distinguished a "MSI Standard M/B." motherboard from a "mainboard with "CPU PLUG AND PLAY" function." but the BIOS for the latter was newer by several months so i finally tried it .. and then was unable to boot back into the BIOS, and had no chance to boot with a floppy to flash it back to a 's'-prefixed BIOS. My board is a 1.1 version, "MS6119 ver 1.1 BX2" and it has a DIP switch-device on the motherboard marked "SW1" (as can be seen in the manual) to set the CPU-speed. I couldn't make out from the manual if the "CPU PLUG AND PLAY"-kind motherboard lacked this DIP Switch or not. So, unless you want to try out hot-flashing BIOS'es .. beware! SignatureNah-ah. I'm staying out of this. ... Now, here's my opinion. Please followup in the newsgroup. E-mail address is invalid due to spam-control. > > <snipped previous post messages to simplify things a bit> > [quoted text clipped - 60 lines] > > - Show quoted text - I am going to heed your warning advice - I have decided not to flash the BIOS because I think the likelihood of success is too small and the likelihood of a fundamental problem is too large. Thank you, Best regards, Robert. > Inside Win98SE's "pure DOS", when I run the DOS utility called > "nvram120.exe", I see the subject line error on screen, and then I [quoted text clipped - 65 lines] > Phew, that's it I think. Sorry for the long post! Thanks for any > suggestions at all. Best regards, Robert. Thanks a lot Brian, Philo, MEB and Franc for your helpful comments! To summarise, ATM I have removed some cards leaving this config: All 3 ISA slots filled with non-PnP sound cards. PCI Slot #2 = graphics card. AGP = graphics card. I'm having no probs at all with the two graphics cards, no problems with the BIOS, no Win98 problems either. I can now run nvram120.exe if I don't use emm386. However, it doesn't provide any information about the 3 non-PnP ISA sound cards. This may be normal, I'm not sure. Although I am getting no errors with any of the 3 non-PnP sound cards, when I added in the 3rd card (an AWE32), it now makes the 1st card (Roland SCC-1) either silent or occasionally it outputs very incorrect sounds. Regarding this soundcard problem, I think I might post this on a soundcard google groups site, but in case anyone is interested, the problem is summarised below - Roland SCC-1 ~ IRQ=3, I/O=330. Works fine if AWE32 is not present, otherwise is silent. GUS Classic ~ IRQ=7 and also 7 for SB emulation (which I don't use), I/O=240, DMA=3 (playback) and 3 (recording). Usually works fine with all other soundcards, very occasionally goes silent. Creative AWE32 ~ IRQ=5, I/O=220 and 300 (disabled MSEL jumper to avoid 330 which would clash with Roland SCC-1), 620 (awe effects), DMA=1 and 5. I also disabled the joystick and MPU-401 jumpers hoping that would help matters.) Works fine with all other soundcards. Problem summary = Roland SCC-1 does not cause any errors as such - it's just silent now the AWE32 is in place. Thanks again, Best regards, Robert. <snipped for brevity> > To address some of the issues above, in Windows98SE I decided to > Disable NVRAM/ESCD updates inside Plug and Play BIOS properties inside [quoted text clipped - 33 lines] > Phew, that's it I think. Sorry for the long post! Thanks for any > suggestions at all. Best regards, Robert. Thanks a lot Brian, Philo, MEB and Franc for your helpful comments! To summarise, ATM I have removed some cards leaving this config: All 3 ISA slots filled with non-PnP sound cards. PCI Slot #2 = graphics card. AGP = graphics card. I'm having no probs at all with the two graphics cards, no problems with the BIOS, no Win98 problems either. I can now run nvram120.exe if I don't use emm386. However, it doesn't provide any information about the 3 non-PnP ISA sound cards. This may be normal, I'm not sure. Although I am getting no errors with any of the 3 non-PnP sound cards, when I added in the 3rd card (an AWE32), it now makes the 1st card (Roland SCC-1) either silent or occasionally it outputs very incorrect sounds. Regarding this soundcard problem, I think I might post this on a soundcard google groups site, but in case anyone is interested, the problem is summarised below - Roland SCC-1 ~ IRQ=3, I/O=330. Works fine if AWE32 is not present, otherwise is silent. GUS Classic ~ IRQ=7 and also 7 for SB emulation (which I don't use), I/O=240, DMA=3 (playback) and 3 (recording). Usually works fine with all other soundcards, very occasionally goes silent. Creative AWE32 ~ IRQ=5, I/O=220 and 300 (disabled MSEL jumper to avoid 330 which would clash with Roland SCC-1), 620 (awe effects), DMA=1 and 5. I also disabled the joystick and MPU-401 jumpers hoping that would help matters.) Works fine with all other soundcards. Problem summary = Roland SCC-1 does not cause any errors as such - it's just silent now the AWE32 is in place. Thanks again, Best regards, Robert. Glad you are making some progress. The non- PnP cards usually have jumpers on them for assigning resources and can usually be made to work...eventually... however due to such hassles, I tend not to use more than one ISA card per machine... if I have sufficient PCI cards/slots avail >The non- PnP cards usually have jumpers on them for assigning resources >and can usually be made to work...eventually... >however due to such hassles, I tend not to use more than one ISA card per >machine... >if I have sufficient PCI cards/slots avail There was an intermediate period where jumperless non-PnP cards were in vogue. These were configured using DOS based configuration utilities, usually via the autoexec.bat file. I have one of these cards in an old Win95/486 box. The card has no Win95 drivers, but it can be made to work by configuring it in Sound Blaster mode and then allowing Windows to detect it as such. - Franc Zabkar SignaturePlease remove one 'i' from my address when replying by email. > > Inside Win98SE's "pure DOS", when I run the DOS utility called > > "nvram120.exe", I see the subject line error on screen, and then I [quoted text clipped - 107 lines] > > - Show quoted text - Just to update the ISA sound card situation: If I remove the AWE32, and replace it with a legacy SB16, *everything* works. (ie, I get the Roland SCC-1 working fine, and the SB16 also works fine too. Plus the GUS works as well!) The legacy SB16 has the MSEL jumper set to open which means the midi address = 300 and not 330. The SB Diagnose utility accepts this value OK no problems. However, if I insert the AWE32 card back in the PC (with the MSEL jumper also set to open, which means the midi address is 300 and not 330), and then run the Diagnose utility, Diagnose reports a problem and will not accept 300 as a valid midi address. Strangely it accepts 330, even though the MSEL midi jumper is set to open which is 300. Regards, Robert. Out of curiosity, why three sound cards? The AWE32 uses more resources [IRQ and physical addresses] than the base 16bit cards do. Its also a bit more particular with "sharing" those resources even when re-configured to supposed free or non-conflicting resources.. Its use of time slices and memory allocation is also more restrictive and demanding. Its related, in part, to 32bit verses 16bit issues and how Windows assigns priority. If you checked the NET you have found that the AWE32 does and did cause issues in certain systems and configurations, and specific versions [country specific or other] each had their own quirks.. With your three card configuration, you have compounded all the underlying issues that might be involved. Its also possible that the physical drivers are causing actual memory assignment conflicts [memory being used beyond the LINK/stub [that's not the actual terms, but might be understood more easily] base addresses that are shown in the configuration], over-writing the others requests. Windows 9X likes to run certain activities in certain areas of memory, when two or more are in conflict, one gets "lost" or held in waiting, or just not run if it can't be re-assigned elsewhere. But beyond that, it isn't all that unusual to find adapters [and other devices] that will not work together, be it video, network, scanners, or other. You MIGHT be able to get the issues resolved by complete MANUAL configuration of the slots in the BIOS [no plug and pray, no PnP assigned addressing or OS] AND by manually configuring EACH card and adapter BY SLOT within Device Manager, but a single crash [BIOS or system], and you would likely be back to manual reconfiguration all over again. Windows doesn't like it when it doesn't have control,, it "usually" retains the information for one or two manually set cards [but not always], but when everything is manually setup, it gets confused. And the first time the Find New Hardware is run [by you or the system], its back to conflicts and things that don't work as Windows has no idea how to configure the system, and much of its *virtual* aspects have been essentially broken. Don't take this wrong, you could or can, perhaps, get this to work, but long term stability is questionable. SignatureMEB http://peoplescounsel.orgfree.com -- _________ > > Inside Win98SE's "pure DOS", when I run the DOS utility called > > "nvram120.exe", I see the subject line error on screen, and then I [quoted text clipped - 107 lines] > > - Show quoted text - Just to update the ISA sound card situation: If I remove the AWE32, and replace it with a legacy SB16, *everything* works. (ie, I get the Roland SCC-1 working fine, and the SB16 also works fine too. Plus the GUS works as well!) The legacy SB16 has the MSEL jumper set to open which means the midi address = 300 and not 330. The SB Diagnose utility accepts this value OK no problems. However, if I insert the AWE32 card back in the PC (with the MSEL jumper also set to open, which means the midi address is 300 and not 330), and then run the Diagnose utility, Diagnose reports a problem and will not accept 300 as a valid midi address. Strangely it accepts 330, even though the MSEL midi jumper is set to open which is 300. Regards, Robert. > Out of curiosity, why three sound cards? (Thanks a lot for your help and information.) I'm passionate about trying to get legacy hardware (especially sound cards) to work inside Windows 98 and it's real mode DOS environment, and so if I can successfully get as many sound cards working inside a PC as possible, then I've got as much choice as possible when it comes to selecting which type of sound card is used for which type of software. (I'm trying to build three legacy Win9x PCs, and hope to have a grand total of 11 sound cards to choose from, to give me a really great choice of sounds!) Apart from one very minor quirk (which I don't think is too important), I have now got these 3 ISA cards all working together: #1 Roland SCC-1 #2 GUS Classic #3 AWE32 My next challenge is to add two more PCI cards to this PC I'm currently working on (one is a 3dfx card, the other is a sound card), and then that will be every slot filled, which includes a USB ethernet gadget to allow for LAN and internet access. In regards to the PCI sound card I wish to insert next, I'm bracing myself for a whole world of pain because it's a Creative/Ensoniq 1371 AudioPCI card which I think will cause bedlam by installing a legacy DOS software driver which I don't require, and will also ruin my auto/ config files. Actually, please can you offer some guidance about this -- is it possible to just install the 1371 card's "main win9x driver" only, without the other extra device drivers being installed as well (I think it also installs something called Gameport, and as previously mentioned a Legacy DOS Driver). This isn't too much of a problem I think, because I guess these additional drivers can always be disabled (or hopefully removed entirely) inside Device Manager. But something that I have never found an answer to (possibly because I'm too stupid), is how do you prevent software driver packages constantly meddling with your auto/ config files without your knowledge or permission? I'm really concerned that installing the 1371 card driver package will mess up my carefully configured auto/config files, but even worse, even if I undo the meddling which has been done by the driver package installation, I'll never be able to stop the software drivers undoing my corrections to their meddling! This has been something that has driven me nearly insane in the past, and I'd love to finally be able to understand how to get around it. Thank you very much, best regards, from Robert. Another one in the same system,, wow.. I still see no purpose... I do see and appreciate the testing you're doing though.. remember that each OS will react differently and the outcome will be affected by what motherboard/chipset, BIOS, differing devices, and other that are intended in those configurations. What works for you may not work for others. Okay, whatever driver installer you use, it generally has configuration files with it. Modifying the INF(s) and/or other files manually, allows [or generally does] the installer to be setup to your particular needs. Issues develop when your desired settings are either not supported by the driver itself or the hardware, or unknowingly conflicts with some base system requirement. Basically, the information you seek [chip requirements and code, Windows relationships, etc.] is EXACTLY what the original driver programmers also required and created their programs around [if you want to avoid trial and error, good luck finding this]. There are times when you can modify their pre-written drivers [if necessary] using various tools to change bits of code, but that is referred to generally as reverse engineering and/or violation of copyright law [coding is difficult for courts to handle], which may be or is generally found as bordering on or is illegal. Its doubtful there would be difficulties [legally] unless you offered them for sale [private use modifications have been done for years in large corporations or networks] or posted them online [but of course some do, remember though your modifications may trash someone else's system], however the original company/manufacturer can take issue if it chooses to do so. There are also tools sometimes available, as you found, to reset the hardware [if applicable and supported] "hard" set requirements, as well as debug routines and other which could also be applied.. That out of the way, first try opening the installer and looking for the INFs and other setup files, and modify [by trial and error] the entries to suit your purpose. If nothing works or you "break the system" {which is what will generally occur} start from scratch [make sure to cleanup the registry]. NOTE: sometimes the card MAY require DOS to pre-initialize the card, prior to final setup in Windows or its use, or it may be part of what is required for Window's drivers to work.. This is similar to the modification made to something such as AOL's installer and its INFs and other, which removes the AOL browser, Real Player, QuickTime, and other aspects, yet still allows the installation, private network, and other use. Lots of good resources available on the Internet for modifying drivers... and dozens of forums devoted to that purpose. SignatureMEB http://peoplescounsel.orgfree.com -- _________ On 26 May, 18:50, "MEB" <meb@not h...@hotmail.com> wrote: > Out of curiosity, why three sound cards? (Thanks a lot for your help and information.) I'm passionate about trying to get legacy hardware (especially sound cards) to work inside Windows 98 and it's real mode DOS environment, and so if I can successfully get as many sound cards working inside a PC as possible, then I've got as much choice as possible when it comes to selecting which type of sound card is used for which type of software. (I'm trying to build three legacy Win9x PCs, and hope to have a grand total of 11 sound cards to choose from, to give me a really great choice of sounds!) Apart from one very minor quirk (which I don't think is too important), I have now got these 3 ISA cards all working together: #1 Roland SCC-1 #2 GUS Classic #3 AWE32 My next challenge is to add two more PCI cards to this PC I'm currently working on (one is a 3dfx card, the other is a sound card), and then that will be every slot filled, which includes a USB ethernet gadget to allow for LAN and internet access. In regards to the PCI sound card I wish to insert next, I'm bracing myself for a whole world of pain because it's a Creative/Ensoniq 1371 AudioPCI card which I think will cause bedlam by installing a legacy DOS software driver which I don't require, and will also ruin my auto/ config files. Actually, please can you offer some guidance about this -- is it possible to just install the 1371 card's "main win9x driver" only, without the other extra device drivers being installed as well (I think it also installs something called Gameport, and as previously mentioned a Legacy DOS Driver). This isn't too much of a problem I think, because I guess these additional drivers can always be disabled (or hopefully removed entirely) inside Device Manager. But something that I have never found an answer to (possibly because I'm too stupid), is how do you prevent software driver packages constantly meddling with your auto/ config files without your knowledge or permission? I'm really concerned that installing the 1371 card driver package will mess up my carefully configured auto/config files, but even worse, even if I undo the meddling which has been done by the driver package installation, I'll never be able to stop the software drivers undoing my corrections to their meddling! This has been something that has driven me nearly insane in the past, and I'd love to finally be able to understand how to get around it. Thank you very much, best regards, from Robert. > Another one in the same system,, wow.. I still see no purpose... I do see > and appreciate the testing you're doing though.. remember that each OS will [quoted text clipped - 43 lines] > -- > MEBhttp://peoplescounsel.orgfree.com I think I'm having a very lucky streak ATM because I think I've solved all problems! The following Supermicro P6SBU mobo hardware configuration seems to work with Win98SE: AGP = Matrox G450 PCI slot #4 = Diamond 3dfx voodoo 1 (footnote below labelled *a*3dfx has more info ) PCI slot #3 = Creative/Ensoniq es1371 sound card (footnote *b*es has more info) PCI #2 = Matrox G200 (footnote *c*g200) PCI #1 = nothing, because it's shared with the following Roland ISA card: ISA = Roland SCC-1 ISA = GUS Classic ISA = AWE32 Footnotes: *a*3dfx = Both Win98 and Diamond utility recognise this card OK, but it remains untested within the Win98 environment because the installed Diamond driver is for DX5 only, and I currently have DX7 on my Win98 PC. However, this card will remain where it is because I am about to install Win95 within a "BootIt NG" multi-boot environment, and then I can test this card properly with DX5 (on Win95). *b*es = I opted to disable both the Gameport and Legacy DOS drivers inside Device Manager. However, they appeared to be OK before I disabled them. I don't need a Legacy DOS driver as I have 3 ISA DOS- based sound cards in this PC! *c*g200 = Having a second graphics card (in addition to the AGP card) allows you to switch between these two graphics cards using Win98 hardware configuration profiles, in conjunction with the BIOS's ability to toggle between AGP and PCI hardware display choice. This allows you to use the PCI graphics card plus the PCI graphics accelerator for any 3dfx software you might have, then once you tire of this (alongside the slightly blurry looking "cable pass-thru" arrangement), you can then switch back to the sharper AGP display that does not have the slightly blurry cable pass-thru arrangement, and also uses a better DVI cable too.) As all of the above seems to work, I'm going to save the HDD partition to an external HDD and then start all over again (with the same hardware in the same slots -- adding one card in at a time of course) but with Windows 95. A major concern that I've just had this moment is - does Win95 even support hardware profiles? Best regards, Robert. > > Another one in the same system,, wow.. I still see no purpose... I do see > > and appreciate the testing you're doing though.. remember that each OS will [quoted text clipped - 98 lines] > > - Show quoted text - PS - knew I'd forget a couple of things: One USB port has an ethernet connectivity gadget attached to it. Win98 reports that four free IRQs are available. (I do have both serial and one parallel port disabled inside BIOS because I just don't need them.) On 26 May, 22:08, "MEB" <meb@not h...@hotmail.com> wrote: > Another one in the same system,, wow.. I still see no purpose... I do see > and appreciate the testing you're doing though.. remember that each OS will [quoted text clipped - 43 lines] > -- > MEBhttp://peoplescounsel.orgfree.com I think I'm having a very lucky streak ATM because I think I've solved all problems! The following Supermicro P6SBU mobo hardware configuration seems to work with Win98SE: AGP = Matrox G450 PCI slot #4 = Diamond 3dfx voodoo 1 (footnote below labelled *a*3dfx has more info ) PCI slot #3 = Creative/Ensoniq es1371 sound card (footnote *b*es has more info) PCI #2 = Matrox G200 (footnote *c*g200) PCI #1 = nothing, because it's shared with the following Roland ISA card: ISA = Roland SCC-1 ISA = GUS Classic ISA = AWE32 Footnotes: *a*3dfx = Both Win98 and Diamond utility recognise this card OK, but it remains untested within the Win98 environment because the installed Diamond driver is for DX5 only, and I currently have DX7 on my Win98 PC. However, this card will remain where it is because I am about to install Win95 within a "BootIt NG" multi-boot environment, and then I can test this card properly with DX5 (on Win95). MEB- Ah sure, I happen to have two Voodoo2 cards SLIed in this machine. You want to test with the best [highest supported] DirextX and Voodoo drivers supported within the target OS. Try the Voodoo/3DFX reference drivers instead of the Diamond drivers and up the DirectX to Version 7 or 8 [98 or SE], and see if your DX4-5 and Diamond driver blurriness disappears. IF it was a Voodoo2 I would have recommended the rkv2dx6.exe for a start. IF you really want to see what can be done, try the MESA, FastVoodoo, or other un-official drivers. http://www.downloadsource.net/c108/3DFX/ or http://www.voodoofiles.com/category.asp?x=13 -------- *b*es = I opted to disable both the Gameport and Legacy DOS drivers inside Device Manager. However, they appeared to be OK before I disabled them. I don't need a Legacy DOS driver as I have 3 ISA DOS- based sound cards in this PC! MEB- What does having three cards have to do with whether you need a DOS driver? IF you're not using those ports, then sure, disable them. IF you're not ever going to use DOS, then sure, attempt to disable or remove the DOS drivers. IF you WERE going to use DOS, then only one card DOS driver would be used. --------- *c*g200 = Having a second graphics card (in addition to the AGP card) allows you to switch between these two graphics cards using Win98 hardware configuration profiles, in conjunction with the BIOS's ability to toggle between AGP and PCI hardware display choice. This allows you to use the PCI graphics card plus the PCI graphics accelerator for any 3dfx software you might have, then once you tire of this (alongside the slightly blurry looking "cable pass-thru" arrangement), you can then switch back to the sharper AGP display that does not have the slightly blurry cable pass-thru arrangement, and also uses a better DVI cable too.) MEB- Right. I have a PNY GFX 5500 as the master card [PCI by the way as this AGP 2.0 version has a minor bug {ABIT BX6R2, actually the bug is in Award BIOS 4.51PG} and limited support for the 2.0 standard. AGP 2.0 true support is becoming difficult to find in video cards. Again, update the system drivers to see if your blurriness goes away. ------ As all of the above seems to work, I'm going to save the HDD partition to an external HDD and then start all over again (with the same hardware in the same slots -- adding one card in at a time of course) but with Windows 95. A major concern that I've just had this moment is - does Win95 even support hardware profiles? MEB- Oh wow, those Win95 memories for me are gone [long ago replaced]...there is at least one 95 user monitoring here, so don't feel you can't post here with questions or other... any physical information/data from that era was LONG ago packed away. You also may want to do those 98 updates since you appear to want information for later use. --------- Best regards, Robert. MEB- PERSONAL REQUEST- Can I get you to do something for the group or at least me? How about using a different message format, the quoted-printable messes up quoting in OE [which I still use do to testing]. I know I can fix this with other tools or settings [or reader], but those either install aspects that are NOT standard in a Win98SE base installation or open a hole in the present security setup [hence must be accounted for during testing and monitoring].. Thanks.. ------- BTW: You still haven't explained why you want all these sound cards installed. ------ AND per your other post, its a good thing you disabled the two comm ports and printer port, that freed some resources which WOULD have given you a lot more difficulties [three IRQs and multiple addressing ranges]. The USB aspect is mainly handled "virtually" so though it can at times cause conflicts, yours appears to be being handled correctly. So between the *disabled*: game ports, DOS, comm ports, and printer, you gave yourself a wider berth to place those cards in. SignatureMEB http://peoplescounsel.orgfree.com -- _________ <lots of snipping done to hopefully avoid OE reader problems> Re: voodoo recommendations -> Thanks, I will try them. Re: Win95 -> I've had a massive stroke of luck with this - I simply wiped the (Win98) HDD, left every single hardware component where it was (from the successful Win98 installation), installed Win95 and almost everything worked first time! A few things I didn't need didn't work, but that's OK! Re: using a different message format -> Actually, I'm not too sure what to do here. I use google groups to do all of this posting message stuff. I'm not sure if you have any control over formatting. I must learn to use a client-based newsgroups reader! (I don't think I've ever used one in my life - I've heard that using google groups is really bad, but I still use it. I must be an idiot.) In the meantime, I hope you can read this reply OK without it messing up your OE. Re: "You still haven't explained why you want all these sound cards installed." -> It's just that for DOS software, I want a lot of choice when it comes to selecting the music and sound effects simply because it's fun to be able to listen to music on various different (ISA) cards. And I also wanted a (PCI) Windows 9x-based sound card too for things like EAX, 3D sound, etc. Really it just boils down to having some fun with lots of different sound options to play around with. Thanks, best regards, Robert. ><lots of snipping done to hopefully avoid OE reader problems> > [quoted text clipped - 6 lines] >I've heard that using google groups is really bad, but I still use >it. I must be an idiot.) Web based news readers are slow and cumbersome. The good thing about Google, however, is that it maintains a complete archive of the non-binary groups. >In the meantime, I hope you can read this reply OK without it messing >up your OE. The problem is at OE's end. OE doesn't know how to properly quote "quoted printable" formats. AFAIK there is a fix for this, but not many OE users bother to install it. - Franc Zabkar SignaturePlease remove one 'i' from my address when replying by email. Can't in this installation, its a base test installation being used to test Live access, and browsers supported. SignatureMEB http://peoplescounsel.orgfree.com -- _________ | ><lots of snipping done to hopefully avoid OE reader problems> | > [quoted text clipped - 19 lines] | | - Franc Zabkar >>In the meantime, I hope you can read this reply OK without it messing >>up your OE. > >The problem is at OE's end. OE doesn't know how to properly quote >"quoted printable" formats. AFAIK there is a fix for this, but not >many OE users bother to install it. This *may* be a possible fix for OE: http://home.in.tum.de/~jain/software/oe-quotefix/ Here is one MS document that explains why OE is designed to (mis)behave the way that it does: http://support.microsoft.com/kb/q168779/#appliesto - Franc Zabkar SignaturePlease remove one 'i' from my address when replying by email. | <lots of snipping done to hopefully avoid OE reader problems> | [quoted text clipped - 9 lines] | everything worked first time! A few things I didn't need didn't work, | but that's OK! Like no USB 2.0, needing to install motherboard drivers, and other later updates found in SP1/Win98-SP2/SE. | Re: using a different message format -> | [quoted text clipped - 7 lines] | In the meantime, I hope you can read this reply OK without it messing | up your OE. My bad, though I looked at the message header, I walked right by the googlegroups [duh for me]... Why not use a direct connect to the group with your news reader? {Apparently you were using the Google web interface?} Been awhile since I set up Google, seems there was a way to declare type or UTF-8 in User Settings or News reply... maybe not.. | Re: "You still haven't explained why you want all these sound cards | installed." -> [quoted text clipped - 7 lines] | | Thanks, best regards, Robert. Oh, I can relate to that, one of those been there/done that moments. Its really fun if you can find the different "sound packs"/extensions for the cards [if available,- reverbs, echoes, etc..].. I had an old MediaVision card that blew away almost everything else I tried, way better sound than 8bit/16bit Creative's. It was a full blown [complete hardware, its was LARGE] card with lots [comparatively] of configurable memory and mods to play with. SignatureMEB http://peoplescounsel.orgfree.com -- _________ | Re: Win95 -> | [quoted text clipped - 3 lines] | everything worked first time! A few things I didn't need didn't work, | but that's OK! --->>> Like no USB 2.0, needing to install motherboard drivers, and other later updates found in SP1/Win98-SP2/SE. Yes, the USB didn't work at all. However, ATM this is very low priority, and I'm happy to leave this for now and then try a website such as usbman and look thru their troubleshooting guide to figure out why. But really for now, it's no big deal at all because the "Win95 side-project" is less important than the Win98 stuff. I think the motherboard drivers installed OK actually. The Intel 440 chipset drivers installation appeared to be successful. Going very briefly back to the (Win95) USB theme, When I ran the MS USB supplement package to get USB on to Win95, I noticed on reboot an error message flashed up on the screen extremely quickly saying something like "bad command or filename". | It's just that for DOS software, I want a lot of choice when it comes | to selecting the music and sound effects simply because it's fun to be [quoted text clipped - 4 lines] | | Thanks, best regards, Robert. --->>> Oh, I can relate to that, one of those been there/done that moments. Its really fun if you can find the different "sound packs"/extensions for the cards [if available,- reverbs, echoes, etc..].. I had an old MediaVision card that blew away almost everything else I tried, way better sound than 8bit/16bit Creative's. It was a full blown [complete hardware, its was LARGE] card with lots [comparatively] of configurable memory and mods to play with. You're making me want one of these things now!! lol. Best regards, Robert. | | Re: Win95 -> | | [quoted text clipped - 22 lines] | error message flashed up on the screen extremely quickly saying | something like "bad command or filename". Had you caight the actual message we might have had something to work from. Did/does USB seem to work? No boot delays or other errors? | | It's just that for DOS software, I want a lot of choice when it | comes [quoted text clipped - 27 lines] | | Best regards, Robert. It was nice,, gave it to the Kids in one of their computers I built for them, and they gave it away or junked it [so much good stuff gets junked, oh well]... SignatureMEB http://peoplescounsel.orgfree.com -- _________ | I think the motherboard drivers installed OK actually. The Intel 440 | chipset drivers installation appeared to be successful. Going very | briefly back to the (Win95) USB theme, When I ran the MS USB | supplement package to get USB on to Win95, I noticed on reboot an | error message flashed up on the screen extremely quickly saying | something like "bad command or filename". --->>> Had you caight the actual message we might have had something to work from. Did/does USB seem to work? No boot delays or other errors? Please note that getting USB to work on Win95 ATM is very low priority. Apart from the USB issue, I was really thrilled that so much worked (and with such little effort) under Win95. However, now I am very satisfied I've got the majority of things working on the current mobo with both Win98 and Win95 (hardware profiles, 3 ISA sound cards, 4th (PCI) sound card, 2 graphics cards, plus a 3dfx card), I am now going to store the mobo away for a short period of time so that I can concentrate back on good ol' Win98 with a "brand new" mobo - this time a QDI BrillianX, and see how I get on with that. This time, I got a whole new array of bits to stick in this one (a load more sound cards both ISA and PCI, two more graphics cards, some SLI voodoo2s, and another USB ethernet gadget), so it's going to be a whole new learning experience! No doubt I'll be posting one or two questions about it...probably tomorrow morning! lol. To answer your question about Win95 & USB, after performing the USB install (both the MS USB initial supplement and the MS USB update package), USB never worked at all - nothing ever appeared inside Device Manager pertaining to USB at all. (EDIT---no wait a minute something called PCI Universal Serial Bus was there with a "?" symbol next to it.) Also, there are no boot delays or errors. (Please note the Intel chipset driver package appeared to install ok straight after I fresh-installed Win95.) But as I say, I can go back to that and solve it after I do the much more important Win98 stuff. Actually, once I get Win98 working on the "new" QDI board, I'm going have another go at Win95, so I'll put it on after I get Win98 working. (I've just bought BootIt NG, so I can also try that out too.) Once Win95 is on, I'm going to have another go at USB. Thanks a lot, Best regards, Robert. Oh, okay, 95 issues are on the back burner then... If you get the chance, you might want to search Google or your favorite search engine for USB in 95 issues and save yourself some time. SignatureMEB http://peoplescounsel.orgfree.com -- _________ On 28 May, 18:46, "MEB" <meb@not h...@hotmail.com> wrote: | I think the motherboard drivers installed OK actually. The Intel 440 | chipset drivers installation appeared to be successful. Going very | briefly back to the (Win95) USB theme, When I ran the MS USB | supplement package to get USB on to Win95, I noticed on reboot an | error message flashed up on the screen extremely quickly saying | something like "bad command or filename". --->>> Had you caight the actual message we might have had something to work from. Did/does USB seem to work? No boot delays or other errors? Please note that getting USB to work on Win95 ATM is very low priority. Apart from the USB issue, I was really thrilled that so much worked (and with such little effort) under Win95. However, now I am very satisfied I've got the majority of things working on the current mobo with both Win98 and Win95 (hardware profiles, 3 ISA sound cards, 4th (PCI) sound card, 2 graphics cards, plus a 3dfx card), I am now going to store the mobo away for a short period of time so that I can concentrate back on good ol' Win98 with a "brand new" mobo - this time a QDI BrillianX, and see how I get on with that. This time, I got a whole new array of bits to stick in this one (a load more sound cards both ISA and PCI, two more graphics cards, some SLI voodoo2s, and another USB ethernet gadget), so it's going to be a whole new learning experience! No doubt I'll be posting one or two questions about it...probably tomorrow morning! lol. To answer your question about Win95 & USB, after performing the USB install (both the MS USB initial supplement and the MS USB update package), USB never worked at all - nothing ever appeared inside Device Manager pertaining to USB at all. (EDIT---no wait a minute something called PCI Universal Serial Bus was there with a "?" symbol next to it.) Also, there are no boot delays or errors. (Please note the Intel chipset driver package appeared to install ok straight after I fresh-installed Win95.) But as I say, I can go back to that and solve it after I do the much more important Win98 stuff. Actually, once I get Win98 working on the "new" QDI board, I'm going have another go at Win95, so I'll put it on after I get Win98 working. (I've just bought BootIt NG, so I can also try that out too.) Once Win95 is on, I'm going to have another go at USB. Thanks a lot, Best regards, Robert. > > > Inside Win98SE's "pure DOS", when I run the DOS utility called > > > "nvram120.exe", I see the subject line error on screen, and then I [quoted text clipped - 127 lines] > > - Show quoted text - Problem solved!! This is what is needed to be done (in case anyone else needs this information) - If you are using soundblaster awe32 model ct2760 revision 3 card (must be this card model and revision number, no other card or model applies!), then do the following - Get 2760r3cd.exe from here - http://ftp4.de.freesbie.org/pub/misc/creative/creative/drivers/sb16awe/ Look at your card and find jumper J1 (which is labelled EEPROM) - it's in the bottom left hand corner, next to jumper J2 (which is labelled MSEL.) Close this J1 jumper, so it's enabled/covered. (Also, open/uncover the J2 jumper right next to it which is labelled MSEL in order to get midi port address to be 300 and not 330.) Extract the files inside 2760r3cd.exe to your soundblaster subfolder (such as c:\sb16). (To extract the files simply run the .exe) Then run setcard.exe This will allow you to configure your midi address from the default 330 to 300. Follow the extremely easy instructions on screen to set your midi base address to be 300. Then turn off your machine (it tells you to do this next.) Uncover jumper J1 again (which is labelled EEPROM). Turn on your machine. That's it, all done. Your card has been reprogrammed to allow your midi port address to be 300 and not 330. Best regards from Robert. So the SB tool worked, okay, I stand corrected in this circumstance.. Thanks for posting the resolution. SignatureMEB http://peoplescounsel.orgfree.com -- _________ > > > Inside Win98SE's "pure DOS", when I run the DOS utility called > > > "nvram120.exe", I see the subject line error on screen, and then I [quoted text clipped - 127 lines] > > - Show quoted text - Problem solved!! This is what is needed to be done (in case anyone else needs this information) - If you are using soundblaster awe32 model ct2760 revision 3 card (must be this card model and revision number, no other card or model applies!), then do the following - Get 2760r3cd.exe from here - http://ftp4.de.freesbie.org/pub/misc/creative/creative/drivers/sb16awe/ Look at your card and find jumper J1 (which is labelled EEPROM) - it's in the bottom left hand corner, next to jumper J2 (which is labelled MSEL.) Close this J1 jumper, so it's enabled/covered. (Also, open/uncover the J2 jumper right next to it which is labelled MSEL in order to get midi port address to be 300 and not 330.) Extract the files inside 2760r3cd.exe to your soundblaster subfolder (such as c:\sb16). (To extract the files simply run the .exe) Then run setcard.exe This will allow you to configure your midi address from the default 330 to 300. Follow the extremely easy instructions on screen to set your midi base address to be 300. Then turn off your machine (it tells you to do this next.) Uncover jumper J1 again (which is labelled EEPROM). Turn on your machine. That's it, all done. Your card has been reprogrammed to allow your midi port address to be 300 and not 330. Best regards from Robert. >Problem solved!! This is what is needed to be done ... > >Look at your card and find jumper J1 (which is labelled EEPROM)... > >Close this J1 jumper, so it's enabled ... >Then run setcard.exe This will allow you to configure your midi >address from the default 330 to 300. >Then turn off your machine ... > >Uncover jumper J1 again ... > >Turn on your machine. That's it, all done. Your card has been >reprogrammed to allow your midi port address to be 300 and not 330. I just remembered that I have a jumperless, non-PnP, NE2000 compatible ISA network card that needs to be configured in similar fashion, ie by writing to its EEPROM. FWIW, I notice that there are big differences between Rev 3 of your CT2760 and the earlier version. SOUNDBLASTER AWE32 (CT2760 REV. 3): http://www.lemmus.eu/th99/i/C-D/53599.htm Previous jumpered version: http://www.thegreenhouse.us/th99/i/C-D/53601.php http://www.bdn.odessa.ua/manu/creativ/scard/ct2760.html - Franc Zabkar SignaturePlease remove one 'i' from my address when replying by email. > >Problem solved!! This is what is needed to be done ... > [quoted text clipped - 24 lines] > -- > Please remove one 'i' from my address when replying by email. More excellent research Franc, thanks very much!! |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.