Tripredacus

Post OS version! You can use DHCP Reservations, however these can become corrupted. If you use them, make sure to keep a document with your reservations in case you need to delete and re-create them.

Does your XML validate in WSIM? Also, do not install Google Chrome in Audit mode. You won't be able to use it after OOBE without a reinstall, unless Google came out with a special "all users" version of Chrome by now.

To add to the conversation about the re-arms. I will say that it "may" be possible to re-arm / generalize more than three times BUT it may only be available if you use an unattend option. I tried to re-arm an image last week that was done with just a regular install, and it returned an error. I didn't think it would work anyways.

You may want to try the official Intel driver instead. I have had no problems with this device. I always get these "two" devices mixed up, MEI, AMT, SOL, WOE... Intel uses all sorts. Different HwIDs have different driver package downloads, yet use the same INF name. WOE HwIDs for H55 platform: VEN_3B67 mesrl.inf / mesrle.inf for x64 v6.0.0.1179 VEN_3B64 heci.inf v6.0.0.1179 WOE HwIDs for Q45 platform: VEN_2E17 mesrl/mesrle.inf v5.5.1.1012 VEN_2E14 heci.inf v5.2.0.1008 The annoying thing is that the v6.x driver series (for Windows 7) does not have driver support for the 2E1x HwIDs, which apparantly only have Vista (v5.x) drivers. So make sure you have the right INFs (since different file versions have the same name but not same hardware support) and check for any signing issues. All the drivers from Intel for these devices (mine are just examples) have signed drivers.

Welcome to the MSFN!

OP, I modified your email address. MSFN shows up on google fairly often, so your email can get searched by bots and send you spam. Especially now that Yahoo IM has had an onslaught of bot activity over the past two weeks.

Welcome to the MSFN!

It's ridiculously simple: cost. Pre-installing the full blown MS Office would add a LOT to the cost. Office 2010 Pro (the not so "limited" version, although that still doesn't include Visio nor Project) would add $300 to the cost of a new PC which is basically as much as some PCs go for these days. How funny! Actually there is a new Office product out there (well it hit with the rest of Office 2010 RTM) called Office Starter. Basically, an OEM can install a trial of Office 2010 Pro on a system. You get three options: 1. Purchase a real version of Office online 2. Use a product key to unlock a particular Office version 3. Install Office Starter, which includes a free (but limited) version of Word and Excel. To my knowledge, the Starter install does not expire. If Starter is installed, you get 2010 Pro for 60 days, and after that, you can only use the Starter apps. http://office.microsoft.com/en-us/starter/ Now, the task of getting it pre-installed on every computer is left up to the OEM. Some have done it already.

I read this in the paper earlier this week. Why can't they just use the existing "fingerprint" known as the MAC Address?

Topics merged! Do not make multiple topics for the same thing.

You can also change the desktop.ini in any folder. I've tried it before and it works but since the desktop.ini can be over-written very easily, sometimes the settings do not stay for very long.

Yes and No. Worst case scenario is that it would install (but not ask for a product key) and not be able to be activated. It depends on the disc, some are made with the same software that is on the recovery partition (cares about hardware) some are generic installs that don't care much about the hardware but couldn't be activated.

I can't find a free version of Macrium. I can only find Macrium Reflect and it only has a 30 day trial. Not sure if that has anything to do with it. You can also try to reactivate your OS in Computer Properties.

Welcome to the MSFN!

Welcome to the MSFN!

You can find the name of it in Device Manager. Common brands are Western Digital, Seagate, Toshiba, etc.

Win98 update pack here: http://www.technical-assistance.co.uk/kb/win98fe-usb-mass-storage-drivers.php Win98se (or ME) usbstor.sys (and other req files for 2.0) modified logo.sys ( I could technically live without this ) win98se ntkern.vxd probably some other stuff, this 98 install is almost 10 years old! PS: other such details (TL;DR) in Project Shiva link in my sig

The Final Plague - What Lies Within

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.