beansmuggler

I guess the independent volume makes sense since the laptop has hardware buttons (though I don't think they work with 98SE). Changing VolumeWidget back to $14 brought both speaker and headphone back to max volume, so I changed it back to $10. I might keep the speaker volume on zero and get a portable speaker with a volume slider as you suggest.

Was able to install dx9c after some trouble (for some reason, my computer only likes it when dx9c is installed from U98SESP3). I'll have to get foobar once I'm certain everything is in place.

The CD audio was from an EXE and I didn't see any source files for it. However, Welcom98.wav claims to be 44100 Hz 4-bit mono, so it might be that the EXE audio was, too. I tested a .WMA rip of Michael Jackson's "Wanna Be Startin' Somethin'" (44100Hz 32-bit? 160kbps stereo) and it played smoothly while left alone. While it was playing, I right-clicked it and chose "Properties" so I could see the codec data for this post. After I clicked that, the song immediately slowed down and then froze in place, and I couldn't move my mouse. I faced some other weird issues after that, which I'm guessing was caused by the file possibly being 32-bit or being WMA. As for Direct Sound output, how would I turn on that setting? I haven't been able to find it yet.

It seems like it glitches on all buffer settings, so I'm guessing it just might be a side effect of everything that runs at startup. I couldn't tell the difference between 5 and 3, so I went with 5 as the safer choice. Strangely enough, the audio popping seems to be almost entirely restricted to system sounds. I played Welcom98.wav in WINDOWS\Application Data\Microsoft\WELCOME and it played with one pop at 5 and no pops at 3. The audio in Whatsnew.exe from the 98SE install CD seemed to play flawlessly under both settings also.

$10 seems to work well, thanks! The audio still has some freezing and glitching on startup, but it pops less now, and playing it in Media Player is mostly clean aside from a few crackles.

Oh, ok! I've added WAVEOUT now and it seems to change HDAcfg, but not the volume. On a restart, the windows sound plays at maximum volume. When I play the sound again in Media Player, it pops 2 or 3 times, then starts playing the sound at a lower volume with less errors (though this might be because it's using the volume slider for Media Player). The Start sound used for clicking on files is played as a single pop/click sound (I'm used to the XP clicking sound, so maybe I'm only confused and nothing is wrong there). All the other sounds play fine in Media Player, though with some quiet electric crackling. I tried reading the datasheet, but I wasn't able to understand it (though I think the copy I found may have been missing some contents) I feel bad asking, but could you look at it when you can?

I started writing a response believing that my setup had failed. As it turns out, I only had a typo: I renamed HDAICOUT.HDA.000 to "HDACIOUT.HDA" instead of HDAICOUT.HDA. I need to be more careful! Anyways, I installed it as instructed (add MinFileCache/MaxFileCache entries to SYSTEM.INI; GENHDA16, HDA2, HDARUN, and HDATSR in HDAFILES; put HDAICOUT.HDA in C:\WINDOWS) on my Dell Latitude D830 and now have working audio but no volume slider in the taskbar. On startup, my speaker pops twice before it plays the startup sound. The Windows startup sound also glitches out a bit while it starts up, making some buzzing noises rather than just cutting out for a bit. My BIOS identifies the Audio Controller as Sigmatel 9205. Dell's website also calls it Sigmatel STAC 92XX, while Siv insists that it's "Intel 82801HBM (ICH8M) HD Audio Controller" with "Vendor ID 8086-284B-01FE1028-02". The only audio-related setting I have in BIOS is to enable and disable the microphone (I'm assuming it's referring to the microphone jack on the side of the machine). One strange thing I've noticed is that the driver causes Windows to report my memory as 1023.0 MB rather than the usual 1024.0 MB. As far as I can tell, it has no other adverse effects. Also, much like when I run DOS on this computer, audio will come out of both the speakers AND the headphones if headphones are plugged in. (As another side note, I happen to own one of those Behringer USB audio devices that was mentioned a few pages back. I'm not sure what they mean by a price spike, since they're still available for about as cheap as I first got it, but it worked fine in my computer as an instant external solution, though I think speakers are needed to take advantage of it. I'm also not sure if it works without updated USB drivers). Here are the contents of HDAcfg and Hdalog: HDAcfg.ini HDALOG.TXT

As expected, 98 won't cooperate with the WiFi drivers available for this device, and I can accept that. I moved on to the USB and ran the Maximus Decim nusb33e update, which seems to work less effectively than I remember last time. I was able to fix the issue by disabling USB Emulation in BIOS (it was re-enabled for convenience in Safe Mode), but I figured I'd keep all the stuff I wrote about it here just in case someone ever needed their issue remedied: At this point, unless I ever want to give the CD issue a shot again (or if anyone else does), I'll move onto the sound drivers, which should be under the proper thread (which I may need to read in full since my installation doesn't seem to be working). Once everything is done, I plan to edit the first post to have a proper installation guide and maybe even a small batch file to help make installation a tad quicker. Thanks to everyone for your help!

While running through the built-in 98SE troubleshooter, I've noticed that it also reboots fine if I was in safe mode, though I guess that's expected since the ethernet seems to cause the problem. I also found an rloew patch for the A: drive issue, so now all my drives are showing as 32-bit (I have the CD disabled for now)! Using the AUMHA site linked on MDGx, I was eventually able to get around the problem by unchecking "Use IRQ Steering" in the Properties for PCI Bus, then switching hardware enumeration to "Use BIOS". As a safety measure, I still installed "Microsoft Windows 98 SE Shutdown Supplement" anyways, and returned the PCI Bus settings to normal ("Use Hardware" and "Use IRQ Steering"). Looks like Ethernet is entirely completed! Moving on to WiFi, I'm going to guess that the Intel Wireless WiFi Link 4965AGN (name given by SIV) is too new for 98SE to handle. So far I've tried the driver provided in Dell's R142718.EXE, but 98 won't recognize it. The one hosted on CNET (which I usually never frequent, but recently heard a success story from) is the same one as Dell's, so no luck there either.

No luck with either option. Reboot to MS-DOS doesn't seem to work, either.

I'm not sure whether it was relocating, trying (and failing) to reinstall, or anything else, but it looks like I'm connected after I moved to a free ethernet connector in another room of the house. I'm guessing I'll need Mozilla or another browser to access MSFN, but it's working! The shutdown problem still seems to persist if I turn it on with the ethernet plugged in. EDIT: Got RetroZilla working properly, so I have access now! Still having the shutdown issue though.

Definite thanks for the find, as it looks like this one was able to install smoothly! I'm still not connected for reasons unknown, but it's at least automatically assigning its own IP address. On bootup, the steady orange light is now accompanied by a few staggered green blips. winipcfg shows nothing in Default Gateway for the ethernet driver even after setting one manually in the settings (it also keeps showing the settings for PPP adapter first rather than Broadcom, not sure if that helps). As soon as I open Internet Explorer, I'm told that I should try working offline instead, and using command prompt to ping 8.8.8.8 results in "Destination host unreachable." Trying to ping google.com instead gets "Unknown host google.com." after a long pause. Also, I can't tell if it's freezing or just taking a long time, but 98 now gets stuck on the "Windows is shutting down" screen during shutdown now. Would I need to apply a shutdown patch, or should this go away once the computer can connect?

Tried this and reinstalled the driver, which it seemed to automatically detect as 57xx Gigabit this time when pointed to the right INF, but it still gave me the warning after reboot. I don't think I've tried to automatically detect with the ethernet drivers listed on the D600 page until now, so I don't know if it would've done this before, but it's at least a good sign since I've usually had to point to these manually.

I've been able to force install the different variants provided by the drivers there so far, but none have worked yet. SIV says what I have is a BCM5755M, which has only provided XP/Vista drivers and discussions about mac/linux so far. On reboot, the loading page hangs while the orange light on the port stays a stable orange with no activity from the green light. After it gives up, it says: On occasion, an installation will fail and cause me to reset with the driver marked with a red X after reboot. If I re-enable the device, it claims to work normally, but it still won't connect to the internet.

Thinking I might shelf the CD thing again until I can get the other things working since it's oddly picky and the MSDOS drivers at least provide a working option. I've kept at the two-step option and tried several different configurations, setup flags, and patch series, but it looks like there's no way to make it cooperate across reboots for now. I tried looking at the manual for the Ultra ATA, but I don't think anything I read would help point out what is going wrong. Since audio seems like it would be the next pickiest to deal with, I figure I'll go with Ethernet first. Something's running on the computer that keeps me from being able to check the BIOS at the moment, but the Internet and some of my other posts seem to say that I either have Broadcom 57XX Gigabit Integrated Controller, 59XX 10/100 Ethernet Controller, or "10/100/1000 Gigabit Ethernet network interface adaptor". Trying to use an INF I found online didn't seem to work out, so I'm guessing I need to be using some kind of software to help connect thru Ethernet. Would I use Odyssey here, or something different?

Got an email back from them and it's apparently a false positive, so I've copied the Power Pack to the computer. The SP1 IE version on it helps get around the issue where MDCU doesn't recognize that I've patched IE, but it still locks up after reboot. Also, I've switched from VIDE-CDD to XGCDROM since MDGx listed it as specifically SATA-relevant.

I tried using Safe Mode for SESP21A, but it still seems to freeze when I boot into normal mode, even after booting into Safe mode. Maybe that has to do with the cocktail of things I do during the 98SE setup process? I noticed it undoes the Safe mode fix so I have to manually re-fix it. Working on getting everything required for MDCU together for now, will note that Windows Security is detecting "Trojan:Win32/Wacatac.B!ml" and "Program:Win32/Wacapew.C!ml" in the MGDx upload of W9xPP 5.01. I downloaded the pack since it has MDIE6CU and MDDACU, which the readme for MDCU says are separate and required for MDCU to work properly.

Where's the safest source to get IE6.0SP1 for MDCU? Also yes, I usually replace the MACHINE/MACHINE2/MSHDC drivers in C:\WINDOWS\INF with the LoneCrusader ones after the first reboot.

Decided to try SESP21A first since it seemed the easiest, but I was never able to successfully boot back into Windows after it finished. I tried the "two stage" method, but I'm stuck on stage 1. The system installed a Standard IDE/ESDI with a Code 10 error. I think this might be caused by a mistake on my part because, even though the PCI Bus was skipped, the system still seems to complain that an A: drive is present. I'll try formatting again and doing a new install. If that doesn't work, I might try AHCICD from rloew since I realize that I never tried that one before. If these fail and nothing else arises, I guess I'll have to concede and move onto the ethernet controller. EDIT: Tried a fresh install and it didn't work, so I tried AHCICD with AHCI. It initially didn't recognize the computer as being in AHCI mode at all, and then later found no AHCI optical disk when I tried specifying controllers, so I guess I'll hold off on pursuing that and accept the compatibility-mode fate. Should one of the DOS long filename patches help ameliorate things at least? Also, is there anything I can try to keep My Computer from trying to read disc contents to generate thumbnail previews when I open My Computer?

After setting it to "No IDE Channels enabled" and restarting my computer, the Ultra ATA let go of IRQ 14 (no device on the system has IRQ 15) and the first two IO ranges, leaving only 6FA0-6FAF. When I install the IDE/ESDI driver, the IDE/ESDI automatically claims the IRQ and IO ranges that were released by Ultra ATA: Input/Output Range 03F6 Input/Output Range 01F0-01F7 Interrupt Request 14 If I choose "No" when Windows asks me to restart, the screen pauses for a second, and then I can go to Device Manager and see the DVD+-RW under the IDE/ESDI, but it will disappear after I reboot. It does not let me change individual resource setting values, but I can choose from 8 different configurations: Configuration 0 is the one shown above. Configurations 2 and 4-6 conflict with Direct access memory controller. Configurations 1 and 7 use IO ranges with IRQ 14 and 15 (if I choose the one with IRQ 15, every configuration except 0 switches to IRQ 15). When I choose any configuration that uses IRQ 15, the exclamation point goes away, but I think that's because nothing's there -- if I set the Ultra ATA to "Both IDE Channels enabled", the Secondary IDE controller uses IRQ 15, while the Primary IDE controller uses 14. When I use any IRQ 14 configuration, it gives a Code 10 error. Funny enough, I decided to try the conflicting configurations, and all of them came up as "No conflict" except for configuration 2. However, they were still stuck under Code 10 errors.

No luck with this one either. It seems to have the same problems as "Primary IDE controller" did, and I cannot change the resources on it. I could get the CD drive to appear if I chose to install the driver without restarting, but it would disappear after a reboot. After trying this a few more ways with some different drivers, I realized that I hadn't looked up the CD drive online, so I popped "HL-DT-ST DVD+-RW GSA-T21N" into Ecosia and found three different revisions on Dell's website. On the driver page for my computer on Dell's site, they listed firmware version A102 as the latest version, though I found a version A103 listed as an older driver after A102 didn't help. I tried each one by doing the resource trick to make the CD drive appear, then running the firmware update until I finally got to A103. In the end, it still didn't work, but I guess this may help with any future fixes. I also realize that I have neglected to state that, when the CD drive appears, it does just that - like my hard drive (not the controller, but the drive itself), it just appears without Add New Hardware appearing to tell me. I assume this is normal, but I'm noting it here just in case.

I tried both of these options but sadly they didn't work. I tried reinstalling and doing these from a fresh install too, but it didn't work out. I tried the NOIDE route, but my registry didn't have NOIDE in it, even after a reinstall. The only note listed on the Performance tab is "Drive A is using the MS-DOS compatibility mode file system", which is strange because I don't have a floppy drive installed. For the resource trick, my Ultra ATA only has one configuration given: Input/Output Range 01F0-01F7 Input/Output Range 03F6-03F6 Interrupt Request 14 Input/Output Range 6FA0-6FAF The last one is shown as 6FA0-6FA7 when looking at the Resources tab on the Primary IDE controller. Since the last field is the only one I'm able to edit, I changed it to 6FE0-6FEF, which was the first available range I found when going upward (under Primary IDE controller, this will show as 6FE0-6FE7). Did a restart and was back to the same problem. From here, I changed the last entry back to 6FA0-6FAF and checked the "Use automatic settings" box. This made the first 2 I/O ranges disappear, changed the last one to 1000-100F (the last range disappears under the resources tab of Primary IDE controller for unknown reasons here), reveals the CD drive, and also creates a Secondary IDE controller (dual fifo) for unknown reasons (funny enough, it will do this even if you explicitly set the Ultra ATA's Dual IDE Channel Settings to "Only Primary IDE Channel Enabled"). After restarting, the Ultra ATA now has the yellow exclamation mark (Primary IDE controller does not appear under it) and it claims to have a resource conflict because it's trying to use the range that was set to System Reserved earlier. I feel like the machine is only working because the resources are actually being changed rather than being on any "correct setting" for some reason, since I can probably choose any range of values and it will work only until I reboot. Maybe I'd need to make a tool that changes the resources after each boot so it shows up? Also, would turning Multi Core Support back on in the BIOS help?

Gave this a shot, but even making the HDD boot dead last so the CD boots first, and booting from hard disk thru the windows 98 disk, it didn't recognize the drive, so maybe it's not timing? Unless something happens in the boot process to ignore it idk It's the "Primary IDE controller (dual fifo)" under "Intel ICH8M Ultra ATA Storage Controllers - 2850" with the yellow exclamation point. The Resource tab for the dual fifo shows "No conflicts.", and it's only after editing the bottom-most value in Resources to another range that the exclamation point goes away, which allows the CD drive to load and appear in Device Manager. The error code in Device Manager is Code 10.

Thanks, I'll have to try those out. One thing I noticed after copying the last 2 vxd's over is that restarting in MS DOS mode allows me access to the CD drive just fine using MSCDEX, though it pauses for a second or two while it waits for the drive to get ready. I think something in normal mode is "impatient" and doesn't wait for the CD drive to get ready, so it fails to recognize it and provides the yellow exclamation mark. A similar thing happens when I start up the computer and choose to boot from CD/DVD: if I choose to boot instantly, it ignores it and goes to HDD booting, but if I wait a few seconds and then choose to boot from CD/DVD, it allows me to do that. If this doesn't work, is there perhaps some setting that would make 98SE wait for the drive to be ready instead of giving up on it?

Completed, but nothing changed. ESDI_506.PDR is still on the 2222 version tho, should I try to update that to 2225 or newer? Also, while I'm not sure if it has any significance, I didn't get a "this file already exists, do you want to overwrite?" warning when copying CONFIGMG, though I did for IOS, though I'm certain they have both been copied to the right place.