Tripredacus

http://www.board-express.com/

The system has been fine with Win98 for many months. The error only happens if I boot into Normal Mode with the Wireless NIC installed. Otherwise it works just fine with the CPU, even when running programs that can use 2GHz. There is no file that it reports with the error. Just says to restart the PC. Today it made me wish there was an Event Viewer on 98. The bootlog.txt/prv have no failures on either a crash or normal boot except it can't load some fonts.

SOAP is a communication protocol used in XML transactions. I am not certain how it related to losing connection to a router. I will move this to the Networking forum for now.

Ha this isn't even legal... OK technically it is a "gray area" for "Dell" to sell an XP Recovery CD with a peice of hardware, but never with a COA, even grayer area for someone who is NOT "Dell" to sell it, and even moreso for someone to buy it from ANYONE selling it. Oh and since the link you guys posted (the MS one this time) is a KB article, this URL works fine on copypasta: http://support.microsoft.com/kb/326246

Even though it completed, the log files should show where the lag happened. I've seen some systems take a long time detecting the display adapter and cause this issue.

If the printer is currently installed on the system, you should see it in Device manager. If you open its properties and go to the Details tab, there is a drop down. If you pick the "Driver Node Strong Name" you will see the line will look like: oem31.inf:blahblahblah The number after "oem" will probably not be 31, that is just an example. But this INF file is the driver that Windows has used for the device. Any drivers that do not come with the OS, or are injected into an install image, or (potentially) added by a driver or Windows Update will be renamed to oem*.inf, where * is the next number sequentially following the highest oem#.inf already in the system. Anyways, this driver actually resides in "C:\Windows\inf" and also there will be a .PNF file with that name also. You can back these up if you don't have the original installer anymore. You now need to prepare the drivers you DO want to use. If they are in a zip file or so, they should be extracted out. You will need to tell Windows where the new INF is located. If it is only in an installer that may complicate things. WinRaR can open some installers like InstallShield. Here is the rest of the process: 1. In Device Manager, uninstall the device and select the "delete driver files" checkbox. 2. Unplug the printer 3. You *may* want to reboot the PC, it doesn't hurt. 4. Plug in the printer 5. When Windows asks for the driver, point it to the driver you prepared earlier If Windows likes that driver, it will install. It still might not, depending on how it was written, or if the driver isn't signed or whatever. Worse case scenario you can install the old driver again until you figure out other ideas.

Isn't this Registry key all that's needed? http://www.windowsitpro.com/article/configuration/how-can-i-view-super-hidden-files-.aspx At this point we do not know if the OP has the same situation as the system I worked on that had the virus on it. I hadn't known about that registry setting before, but these files I found in NTFSDOS would not even show up using a DIR /A:SH which was interesting. Oh I remember another issue that virus-laden PC had. The OS volume would not appear in the lower pane of Disk Management, but would appear in the upper pane.

Oh a notebook, it could be a display issue. Does it do the same thing if it comes out of Sleep Mode? Have you tried Hibernate both on battery and on AC configs? Also play with the "turn off display after" settings to see if you can duplicate this issue with other instances besides Hibernate.

Welcome to the MSFN!

Many people often asked what I took in college, and that was to repair and maintain mainframes and their terminals. Unfortunately the college decided to transition the program in my third semester, so it turned out that I used almost nothing I'd learned in college in my professional career. So you could say I am a dinosaur too!

I've got a dandy of a problem now! So I am trying to get Wireless working on my PC after USB wasn't working I decided to switch to a PCI card. I found one that had drivers and started working on the system today. Here is the issue. When the PCI Card is inserted: - Windows Protection Error - Can only boot into Safe Mode When PCI card is not inserted: - Windows boots into Normal Mode without error. Here are the specs: OS: Win98 FE modified board: Intel D850MV RAM: 768MB RDRAM PC800 CPU: Pentium 4 2.0GHz Video: ATI Radeon 9600XT 256MB AGP Sound: Creative Sound Blaster Live PCI Wireless card: D-Link DWL-G510 PCI I have 5 PCI Slots, and I have tried two of them already. Not interested in moving the SB card at this point. I have tried the following: - Use MSCONFIG to temp disable autoexec.bat (it only has paths), config.sys (OS would not load), win.ini, system.ini and startup programs. - Ran registry checker (no errors) - Ran ASD (1 error, checked and rebooted) - Removed ghost drivers in Safe Mode - Ran step by step, load Win drivers, say N to all. - Set Plug and Play OS in BIOS to No. So I am wondering if this is possibly caused by a resource conflict or lack of resources? If this is so, any BIOS settings that may be helpful? Currently all resource allocation is set to AUTO in the BIOS. I could map the resources out and assign them manually I suppose. Also, the BIOS has onboard sound, parallel port and serial ports set to disabled. I am also worried about running SFC since it may remove the custom files I have. Some updates found on MSFN, some files from Win98 SE and some old hacked files (like logo.sys, etc) so hopefully that won't be an answer. Also a reinstall is going to be out of the question for me. What I will try while waiting for any ideas: 1. Remove LPT and COM devices from Device Manager in Safe Mode 2. Map out used resources in Normal Mode without the card inserted. 3. Try the other 2 slots.

I replaced CODE wit CODEBOX, but the preview looks the same so I have not changed my post. Yeah I later found out that both are semi-bugged.

I'm running out of time to fix up this PC. Tomorrow is the day I will get to work on it again. I have secured a PCI Wireless G card to test with, D-Link DWL-G510: http://www.dlink.com/products/?tab=3&pid=DWL-G510&rev=DWL-G510_revB Has anyone used this one on 98? If this works, I will have to turn G speed back on my router at home, and then my PS3 can go online again too! Speaking of which, is there any media-streaming capabilities between Win98 and PS3? Do you think that the PS3 will be able to see the ShoutCast server once I get that up and running again?

I have noticed that Windows Defender is turned off on my systems that have MSSE installed but I have Windows 7... Also, I found this too: It is from here: http://social.answers.microsoft.com/Forums/en-US/msestart/thread/0f33629e-abf8-4563-83ee-b4977c8d0b23

What hardware did you replace?

This could be an issue with the display. Can you post your video card and display models?

I've seen this type of loss on infected systems. When the HDD is reporting full, see if you can find what folder has the most files. When I ran into this, I found a 40GB Windows folder, but after evaluating the files in that folder, I only found 4GB. You are likely dealing with super-hidden files and folders, which means you can't see them in Windows or from WinPE. I could see them in NTFSDOS. Otherwise you could have a drive that is going bad. You can try running an HD Tester on it, but you'd need to post your hard drive model. Memory dumps (full ones) will take up some space, about 2-4GB but they would take up this space without you knowing it.

The INF for the driver will need to have the HwID for the printer in it. If it is written correctly for the target OS, and there is no other driver file in the system for that HwID, Windows should use that INF to install the driver. I am presuming that you are looking to install this driver into a live OS instead of an image?

Foreigner - Jukebox Hero

Well Blizzard has used server farms for Battle.net as far back as when Diablo II: LOD came out. The exact configuration could be anything really. They could have a couple high-end systems or they could have a hundred mid-range systems. It is still common that the world's fastest computers are actually parallel processing systems that use fairly low-end processors. For example, when Sandia National Labs' Amazing Teraflops Machine went operational, it was made up of a few thousand 200MHz CPUs or something. Actually: http://www.sandia.gov/media/online.htm

The CODE tag has a problem, but CODEBOX works fine in its place. So try using CODEBOX if CODE isn't working for you until this issue is fixed.

First verify that there are not files in this folder: %REMINST%\Boot\x86\Images Where %REMINST% is the path to your RemoteInstallation folder. Second, this information in WDS is not kept in a flat file or in the registry, but in the WDS database. The app WDSUTIL has the ability to modify this information, see if you can remove the boot image by using this tool: WDSUtil Remove-Image As for where the actual database file or what programs can manually edit it, I have not found that out.

That's interesting that Dell would send you (a home user) to here (MSFN) to install your OS (which comes with a 1k per lic/cal price tag) to use nLite (a non-commercial product). In any event SBS Premium 2003 does indeed come on 4 CDs (there's actually more) but I am pretty certain that discs 3 and 4 (and 5 and the Outlook CD, etc) are not required for install. In any case, I know many have had problems combining multi-disc OS installs because at the end of "Disc 1" the install will prompt you to insert "Disc 2" which actually doesn't exist anymore. In the end, if you are using this in your company, be it commercial, government or education sector, you can't use nLite. Its license agreement strictly forbids it. So that being said, why do you need to combine these discs? Is there a specific reason?

It is Microsoft supplied documentation and best practices that say to make them all primary partitions. In order for high-volume OEMs to sell computers with Windows on them, they have to follow strict guidelines but these limitations are still worthwhile to them. As far as the 100MB partition (I've seen them as large as 500MB) that is not for the MBR. The MBR exists before the start of that partition. It is primarily there for BitLocker usage, however if that partition is removed, the BCD will need to be updated in order for Windows to load. As already discussed many times, Windows 7 can work both with and without this partition.