Tripredacus

Hmm it shouldn't change it back on you. That has never happened to me. I had a machine that said it was running OS/2 Warp on a Motorola 8600 through many restarts!

If you feel its the HDD, try disconnecting it and see if it boots to the "can't find OS" message, whatever way it displays that to you. Alternatively, if it does get to this point, you can try replacing the HDD cable and see if that helps. We often find Intel boards that stop at the POST with the dreaded 5A and replacing the cable fixes it 95% of the time.

The other option for getting old games to work in XP is using the Windows Application Compatibility Toolkit. I only used it once, and that was to get the sound to work in Destruction Derby 2, which is a DOS (really W95 DOS Mode) game.

The things that I have noticed that cause slow downs: 1. Explorer updates the volume info for the optical drives 2. The folder nears the FAT limit for individual files.

If your motherboard uses a controller that the XP CD doesn't have a driver for, it will give you this message. You may need to F6 a driver during the install.

iirc all of those strings can be changed in the registry.

Your notebook might be set up to use AHCI which means you can either change it to IDE or use ye olde F6 after you acquire the driver.

I've had mouse problems in the past and these are the things I had tried. 1. See how the performance is while connected using a PS2 adapter. 2. Check your surface compared to the other places it worked. There may be a tolerance difference with the optics. 3. Try connecting that mouse and a different optical USB mouse to the computer, then try to use the other (not the one having problems) and see how it reacts. Sorry I got called into a 3.5 hour meeting when I started writing this email, got brain dead, went home, came back to work and realised I never finished... I hope this helps anyways.

OK I got a new question. I noticed in the HTA itself that there was a "setres" option cfg for 1024x768x32bit. I tried to make it 800x600 but it didn't seem to make a difference. While I did manage to image the ASUS EEE PC 701 with your GUI, it did not support the default resolution and I had to cmd prompt it manually. Is the only thing that is keeping the 800x600 setting at 1024 because of the background PNG?

The only stop errors I have seen with vista are black screens.

I'm just annoyed that it doesn't support full on Boolean like it did when it first came out... Ebay is annoying with the secondguessing as well.

I just tried out the GimageX (COM Based) HTA today and have encountered an error. Line:222 Char:1 Object Required: 'objWIM' Code:0 it is this line: objWIM.Source = myFilepath + objSel1.options(objSel1.selectedindex).text Everything seems to work: I can select images or deploy them, but the image names within the WIM are blank. In my case, there are 2 WIMs and each only has 1 image in them. It shows a radio button after I select the image, but there is no words next to it. EDIT: sorry, I didn't read the part in the first post that said to register the DLL... :\ It works now just fine.

That's queer, I have never seen a VIA EPIA motherboard not being able to boot from USB. Or is it one of those third-party motherboards that use VIA C3? What BIOS (Award or Ami) and version do the machines have? jaclaz It used a Phoenix BIOS. We already shipped the thing so I can't go look at it. It was one of those situations where a USB key wasn't detected by the BIOS as any particular boot option, and you didn't get the ability to select a boot menu. It was not detected as either a Hard Drive, USB-HDD, USB-FDD, USB-CD-ROM or whatever other options there were. We were able to boot off a real USB floppy, and could boot off the USB key if there was no OS on the Hard Drive. It did have an AMI DMI on it tho...

I created a script that defrags a computers 2 volumes and then restarts. I am not using the /noprompt switch because when I did use it, the computer would reboot while it was running. As a test I changed the script to just run the defrag on the one drive, which uses the following cmd: defrag c: /f Now It just has a DOS box up with fragmentation stats on it but doesn't seem to be doing anything. The computer isn't locked up, but the HD LED is on constant. Task Manager shows 00:00 for CPU time for defrag.exe. Is this normal for it to take a long time and not seem to be doing anything??

I did see that actually. Can the computer even go in standby/hibernate while in the PE? Both of these units had their hard drives set for Cable Select. But you should be able to get a computer to boot to the PE even if there isn't a hard drive in it. I've actually done that before...

I am not using a WinPE disc. I use a WDS to boot from the network into the WinPE. And yes, it does work with other machines. Currently it is in a test environment, the one I outlined in my "how to" guide in another thread, so there is rarely more than 1 client computer connected to the network at a time. We also determined that we cannot boot from USB on these units, cannot do a network boot from the PCI NIC and cannot install a CD-ROM drive into it. Because I need to get the other drive imaged, I took its hard drive out and put it into my test client so I can image it that way. However I'd like to keep this thread open because once my company fully switches away from Ghost to WDS, we may encounter this issue again.

I've got 2 identical computers. They both use the EPIA ML motherboard, and have a 60GB IDE hard drive. They both have 1GHz embedded CPU and a VIA Rhine II integrated NIC. One has a blank HDD and the other has a complete install of XP-Pro SP2 with updates and drivers installed. So you can guess I want to capture the complete one and deploy to the blank one. So I have them boot to the network, but I get two different results... The blank one: boots to the following STOP error: STOP 0x000000F4 (0x00000003, 0x844C3AD8, 0x85FB8CD4, 0x00000000) --win32k.sys - Address 85FB8CD4 base at 85E00000 Datestamp 4549aea2 The complete one: boots to a black screen with the mouse cursor on it. You can move the cursor around... Any clues about this? Both have a PCI (Cnet) NIC in them, and I will try booting from those and see what happens...

I will try to remember this in the future. We ended up replacing the drive and reimaging it and it worked that way.

I was imaging up a bunch of notebooks when I came across one that wouldn't boot up. It was in the middle of the image load, meaning there were machines before it and after it that imaged fine. This one machine wouldn't seem to boot into Windows. I restarted and selected the "disable automatic restart on system failure" option from the XP boot menu. On the restart I encountered the following error: SESSION3_INITIALIZATION_FAILED STOP: 0x0000006F (0x6f) I looked online for this error but it all seemed to be related to the install media, with a few references to HDDs. I booted into NTFSDOS and confirmed that the drive was imaged properly. OH my image was applied with WDS not from a CD, on 8 identical build notebooks. 7 work, 1 get this error. Am I to presume that this is a problem with the HDD inside the unit?

Oh btw, this manual is from the ASUS Eee PC 701... since it was in the news, although you could put 1 and 1 together based on my news posting response. ^_^

So every time you open your browser, it would be like playing out an episode of that Connections2 show...

If you have a decent video card that also helps. Try turning off that blur-feature thing that is enabled by default. That helped me a lot iirc when I first got it.

I haven't had any problems with the drivers. I use a Sapphire 256MB Radeon 8600XT AGP 4x/8x

The last program I used to bench Glide was 3dMark2000.

I wanted to post this guide here. I was just tasked with creating a test network where a computer can boot to the network via PXE and load up the WinPE. Hopefully this guide will help someone! NOTE: this is just an example of how to set this up, but after many attempts I found it to be the easiest. What you need to begin 2 Servers running some form of Server 2003 SP1 or better Microsoft Windows AIK Windows 2003 Server disc 1 MSXML6 installer (newest... the one on the AIK iso doesn't always work) 1. Setting up the WDS Server To begin, I took an existing Server 2003 Standard PC to use as the Domain Controller. - set a static IP address that resides outside your projected scope; ie: static 192.168.0.5, projected 192.168.0.10-192.168.0.199. - Follow the instructions on KB 324753 (DC promo) - Create an new user account and assign it to the Domain Users group. - Manage Your Server and add the DHCP role. - Install WDS with Add/Remove Windows components. - run the WDS update from the AIK DVD. - Install MSXML6. - Install .NET Framework 2.0 from the AIK DVD. - follow the instructions to create WinPE boot media. - Open WDS and verify or add your server (itself aka UncleSocks) to the list. - Choose to add a new Boot Image, and select the winpe.wim file from c:\winpe_x86 or wherever you put it. -- Look at the properties of your server and set the following: - On the PXE Response Settings tab: Respond to all (known and unknown) client computers (alternatively you can add known computers to the domain with the AD Users and Computers tool and select the Respond only to known client computers option). - on the Boot tab, change 'x64 architecture' option in the 'Default boot program' section to read 'boot\x86\pxeboot.com' - on the Boot tab, change 'x64 architecture' and 'x86 architecture' options in the 'Default boot image' section to 'boot\x86\images\winpe.wim'. - on the DHCP tab, select 'configure DHCP option 60 to PXEClient' - on the Advanced tab, select 'No, do not authorize the Windows Deployment Services server in DHCP'. 2. Setting up the DHCP Server - set a static IP outside the projected scope ie 192.168.0.6. - join the computer to the Domain using the account you created on the WDS and restart, but log back in as administrator (local). - From Computer Management, go into the groups and add Domain\Domain Users to the COMPUTER\Administrators group. - Log off Administrator (local) and log into the domain. - Manage Your Server and add the DHCP role. - Create a DHCP Scope for the range you want, such as 192.168.0.10-192.168.0.199. - Set the DHCP lease time to 3 hours (the default is 8 days) - make sure your scope is activated. 3. Authorizing the DHCP Server - on the WDS Server, in the DHCP cpl, choose Action->Manage Authorized Servers. - click Authorize and type in the IP address of the DHCP Server. - connect another computer to the network and verify that it can get an IP. 4. Setting up PXE on the DHCP Server - in the DHCP cpl, expand your scope and right Click on Scope Options and select Configure Options. - select option 66 and type in the computer name of the WDS (ie: unclesocks) - select option 67 and type in '\boot\x86\wdsnbp.com' - select option 6 (DNS Servers) and type in the IP for the WDS server. - select option 3 (Router) and type in the IP for the WDS server. With this example you should be able to boot from the network and load up the WinPE from the server. Also this presumes you are going to use Native Mode for WDS. And I realise some security measures weren't taken but this is just a guide. You can set your security up anyway you like really. You can also use whatever WIM you want. For my test I chose the one that the AIK makes. You could very well use a default Vista one or whatever other one you made. I also left out instructions to install the AIK since it isn't supposed to be on the WDS. I installed it on the WDS because I didn't feel like copying it from my workstation, besides I wanted to run through the commands again. That should just about do it. Its kinda annoying because the documentation for this is all over the place. If I left something out, let me know. I just ran this list down from memory o_O Anyways there are a lot of little options dealing with parts of Server that aren't in the WDS that you run into.