jumper

>ISA Sound card stopped functioning (no sound) - device manager suggested a problem - reinstall driver. Some possible causes (and actions to take) for this root problem: CMOS battery died / BIOS IRQ settings changed + Voltage should be at least 2v else replace battery; reset BIOS; set IRQs as needed Registry / drivers corrupted + scandisk HDD to ensure it's not a wider issue + In DOS, "Regedit /restore" last saved registry prior to failure + "Regedit /fix" current registry only if no viable backup Sound card died + shutdown and pull the card + if detection problems for other devices persist, remove ALL hardware (especially mainboard!) drivers in Safe mode + optionally: reinstall sound card once everything else is working and backed-up (if you dare) Mainboard failure: dust in other sockets fried ISA bus; something got zapped; etc. + short term: clean thoroughly; you might be able to run with reduced functionality + long term: replace mainboard I strongly suspect a battery failure, BIOS change, or addition/removal of cards that would change IRQ settings. Most devices are plug-and-play and Windows would adjust, but non-PNP devices such as ISA cards would need redetection. If you did anything in the BIOS or anything inside or outside the case (plugging in or out cards or cables) prior to the sound card failure, please report.

>Would this problem be because of the method I used to update given that I use the latest KernelEx ? Absolutely! But depending on the error, other methods might also produce similiar results. The 12.11 installer may still be on your HDD; it not, download it manually from the Opera site and exit Opera. * Close all other apps and run the installer from Explorer. + You may need to try various KernelEx modes. + You may also need Kexstubs. + You may need to try a portable version of Opera. * You do need to report the text of any error messages so we can figure out how to prevent or avoid them.

Disable KernelEx for the emulator and the plugin. If the problem persists, we'll need to know more about the error. Report all error text including in Details>> or a log file. If none is available, try running the emulator within a light-weight debugger such as Finesse29 to trap the error message.

If your HDD has a large on-board cache, or it is older and slower, then when you shutdown Windows the system may be powering down before the registry is fully flushed (written) from the HDD cache back to the platters. You can try using Regedit to set HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\CacheWriteDelay to 2000 (decimal) or 4000 if already present. Delay is in milliseconds.

>I wish now that I'd not suggested the 50 return code for GetAdaptersAddresses before checking what was documented. Sure, it works fine for SAPGUI, but perhaps the 232 return code would be more appropriate for other applications (and it works fine too for SAPGUI). // // MessageId: ERROR_NO_DATA // // MessageText: // // The pipe is being closed. // #define ERROR_NO_DATA 232L A pipe error probably won't work universally, either. If you have a solution for your apps, don't worry about others--this is just temporary anyway. I'm working on a real implementation derived from the Wine sources. >I notice that all but three functions in this DLL have the same entry point. Given that different functions will have different stack fix-up requirements, I presume that these other functions don't actually do this (properly). So, if any of these other functions are called (eg. HoverIP uses a bunch of functions from IpHlpApi), this DLL would be unsafe. Is that correct? No! You may also have noticed that it doesn't require that the original DLL be copied to another name. It also doesn't require KnownDLL tricks (another way to access the system DLL of the same name). What it does is rewrite its export table at load time to redirect the standard functions to the originals in sysdir. In addition to the stubs (currently) for GetAdaptersAddresses and GetPerAdapterInfo, it also exports a KernelEx-compatible get_api_table. This make it a hybrid Kext DLL that can also be used by KernelEx non-users. I now have a partial implementation of GetPerAdapterInfo working and hope to release it soon. The test plan is to build the MSDN sample code for each API and run it on various platforms, with and without my extension DLL, comparing results.

iphlpapi.zip Unzip iphlpapi.dll into app folder remove HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SessionManager\KnownDLLs\IPHLPAPI entry remove definitions for GetAdaptersAddresses and/or GetPerAdapterInfo from Kexstubs.ini stubs returning E_NOTIMP (0x80004001) for GetAdaptersAddresses and GetPerAdapterInfo will be added to IPHLPAPI in sysdir for just this app. Edit: struck Kex from stubs.ini

I've been having trouble with core.ini processing, also. It doesn't always work they way it appears it should. Even cloning existing profiles isn't reliable. One thing I learned about core.ini mods several months ago is that a full system reboot is necessary between every change--restarting Windows isn't enough. Naturally this greatly slows down the trial-and-error testing! I looked in the source code at how the property sheet changes the mode and think I can write a utility to test each and all profiles to see which will stick if selected after modification (and reboot). Kex changes the mode to default if it doesn't like something about the selected mode. It's been a few months since I looked at the source code for the Core.ini loader. Until I do that again, instead of using a new profile we'll have to stick to modifying the Kexstubs.ini definition on-demand: GetAdaptersAddresses can be changed between r50s5 and t5 immediately before launching an app that needs the other definition. Edit: struck Kex from stubs.ini

>...no way for me to press apply. Press Alt+A to Apply.

A bit of research indicates SUSE has the best change of including X-Fi drivers on the LiveCD. Otherwise, you need to get them from a linux repository and install to a flashdrive (or something.... )

You can also try testing with a different OS. Assuming you don't dual-boot, a Linux live-CD should do....

On the Options tab, check the third box: "Show file version information (slower)"

DISKdata

>Hmmm ... So the only setting so far that is compatible between µTorrent and SAP GUI for Java 7.10r3 is no setting. Too bad the latest Opera doesn't agree with that. For Opera and any other apps that won't load without GetAdaptersAddresses, we'll create two definitions in Kexstubs.ini: [IPHLPAPI.DLL] GetAdaptersAddresses=r50s5 ;.0 GetAdaptersAddresses=t5 ;.1 Then we'll disable them by default in Core.ini: [DCFG1.names.98] IPHLPAPI.GetAdaptersAddresses=none [DCFG1.names.Me] IPHLPAPI.GetAdaptersAddresses=none Then add new profiles in Core.ini to support them: [ApiConfigurations] default=0 0=DCFG1 ... 11=W2KGAA0 12=W2KGAA1 [W2KGAA0] inherit=NT2K desc=Win2K+GetAdaptersAddresses.r50s5 [W2KGAA0.names] IPHLPAPI.GetAdaptersAddresses=Kexstubs.0 [W2KGAA1] inherit=NT2K desc=Win2K+GetAdaptersAddresses.t5 [W2KGAA1.names] IPHLPAPI.GetAdaptersAddresses=Kexstubs.1 As needed: Replace "Kexstubs" with "Kstub822" These new profiles can inherit from any other profile Edit: struck Kex from stubs.ini

It looks like Phaenius is just playing a CD in this test. He should also try the same CD in Windows CD Player as an alternate audio source and compare results.

To the right of the top-left-most arrow is the WinAmp Mute button and then a Volume slider. You have the slider set very low. To get more volume, slide it all the way to the right and Pump Up the Volume! Then turn down the volume at the speakers until it doesn't distort. B) In the picture, the VU meter pointed to by the arrow show no color and appears to also be indicating low playback volume being sent to the system mixer. Press Alt+G to check WinAmp's internal equalizer and preamp levels. >Another thing is the Windows 7 mixer (which I don't get it). I attached a picture. Are you saying that clicking on the Mixer button at the botton of the System Volume control does nothing? Try double-clicking on the Volume control in the systray to open the mixer. Once you find the system mixer, report the levels found there. Make sure you select all volume controls in Options->Properties. You should also explore the Audio tab of the Multimedia Control Panel, especially Playback: Advanced Settings->Performance.

>...and in very low volume it is not audible... Where are you setting the volume: in the application, in the OS mixer, or at the speaker? If you prefer to use the speaker knob as your master volume control, set all volume levels in apps and the audio mixer to as high as possible. Only lower individual source levels in the mixer as needed to balance the sources. Back off the master mixer level only if the audio sounds distorted during loud passages with a low speaker volume setting. Standard troubleshooting: try unpowered speakers connected directly to the speaker jack. try different powered speakers connected directly to the lineout jack. try the LS11 speakers (without extension cable) on a different system or device. test the extension cable with other speakers and on other systems and devices. Report back with results of above four tests!

As a web developer, I've been testing with Opera going all the way back to version 3 and have never considered ANY version of Opera to be stable. I've always wanted to like it, but found too many usability problems with each and every version I tested with.

The Nx speeds are for physical reads/writes. The read cache / write buffer can be accessed at much higher speeds (up to the interface maximum).

The Win98se version of WINTRUST.DLL doesn't contain a function named CryptCATAdminAcquireContext. You either shouldn't be using the WinMe version of SFPDLL.DLL (unlikely), or you also need the WinMe version of WINTRUST.DLL. That file probably also has dependencies.... Try this MDGx page and link for the version of WINTRUST.DLL and other files you probably need: http://www.mdgx.com/ietoy.htm#HEP http://www.mdgx.com/files/CRYPTME.EXE

Glad to hear my lack of History is probably just something wrong with my installation--I've updated post #823. My installation is an upgrade from 10.61 and 10.60 (and maybe over 10.0x). My global_history.dat is 0KB, but get touched each time I exit. I'll try a clean reinstall of 10.63 when I get the chance. Whoever wrote the Wikipedia article must consider the whole 10.6x branch to be unstable....

History does not work [for me] in 10.63. Wikipedia lists 10.54 as the last stable version of the 10.x series. It also lists 10.60 as the first to support WebM video (requires KernelEx).

Forget about the front panel until you confirm the card is working correctly at the back . You need to isolate the "capping" problem.

I suggest downloading from the above links Lenovo's Win98/SE drivers for the 2100 3B and installing it first. You will probably have to select it manually for your card and confirm that you want to use it even though it wasn't written specifically for your hardware. If you can get it to work and are satisfied with 'B'-only speed, you can stop here. The next step is to download Lenovo's Win2K drivers from the above links for the 2100 3B and 2200 BG. Compare the Win2K files (especially inside the *.inf) for the two products to see what drivers changes were made to upgrade from 2100 3B to 2200 BG. Then try to make those same changes to the Win98/SE 2100 3B drivers to create a new Win98/SE 2200 BG driver. If you can create a working driver that did not previous exist, it would be a giant leap forward in our efforts to learn how to create Win9x driver for many modern devices that we can't currently use in Win9x systems!

Check the cabling from the card to the front panel--you could have a floating ground. Is it connected to the correct output (line-out or speaker) ? Try disconnecting the front panel from the card and testing the line-out and speaker outputs directly off the card. Headphones are usually higher impedance than speakers. Check the manual to see what the card supports (without the front panel headphone amplifier). Make sure you test all outputs with appropriate impedance-matched playback devices. The on-card and/or front-panel amps for the headphone and speaker outputs could be blown. The line-outs from the card to self-powered (amplified) speakers or a hi-fi system should provide the best sound quality. The external amplification can then deliver all the volume you desire.

Have you checked the mixer settings for individual levels on each different audio source? You've only mentioned setting the overall volume via various controls.