Ponch

Unless you tell more about what you really want to do, there is not much help needed. As now 1)you have an iso (that I don't think you really downloaded from "MSFN", rather MSDN), 2)you burned it into a bootable cd, (without the need of any .img file) 3)you copied the files from that cd to a directory on your C: drive (be sure you get hidden files copied as well) ... you want to make a bootable cd... the answer is; you have one at point 2). If as we guess, you want to make a custom cd, use nLite on the folder you created in 3), nLite will send you to point 1) creating a new iso (at the end of process, if you choose that option in main menu). You don't need any help (nor any .img file) going from 1) to 2) again as you've just proved you can do it ! Note that there are easy ways to extract an iso without using (wasting) a physical media.

WinSetupFromUSB has a thread of its own (the 2nd sticky here) by its author with lots of info. I know it's quite a long thread ( 85 pages today) but a search on "asms" will get you to post 1225 which points to a possible solution in post 1223.

For AMD CPU, I think the driver integration doesn't work. At least I did not get it working at the time. You can try the addon on this page.

It's all explained in the "Applications Addons" forum (on top of this subsection), but it's requires some reading. But can you provide a link to those two drivers ? It might still be an easier way.

Can you give an example of such a driver ? Usually, if you can "expand" the exe, it does contain .inf file(s) as well, which is what you need.

Funny. I got such an email this week from a friend (also Yahoo) but the client was...... OE6. Though I usually do get his messages OK. I know this doesn't help, just a bit of comfort.

Ok, now you says you are using ASR, I see it needs a floppy to boot to recovery (do you even have a floppy drive ?). At what point does it say that your F: drive will be erased ? Are you launching ASR from the running system (not sure you can do that, probably not, or that's when it says it will restore to F: ? Can you be more precise about what exactly you are trying to do and what exactly you do (what options you use for backuping, from what to what, how you start restore, from what floppy boot or from XP itself) and at what point your problem occures. I get it english is not your 1st language, it's not mine either. But make an effort.

if it ain't broken... We've all been there. Do you have any mean to reapply the manufacturer's image for test ?

Have you tried without cdrom/ hdd/ battery, just motherboard, CPU and memory ? Any mechanical sensor that would prevent it from starting ?

Install what ?

Install what ? I just started XP backup and it seems pretty straightforward, choose what to backup (use 4th option there) and where to save it (as one ".BKF" file). I don't see you running into any problem.

What about the CDs that came with your othe proper keys ?

If it is legitimately copied, why don't you try the original ? Either the media is defective or the copy went wrong.

Can you elaborate on the whole purpose? Do you want to change settings at every boot or more times without rebooting ? For testing purpose ?

This looks so obvious to me I'm afraid I'm missing something.

As said before, (it seems you miss big chunks of my answers), if your install disk does not see the drive, for that exact reason, it won't make it unreadable because it won't touch it. -Install might ask you for computer name when you set same "Owner" and "Computer Name" in Unattended maybe this is the case. -You ticked "Skip OOBE" i Unattended-> that is what causes no prompt for "User"names. -removing components makers install disk smaller, install time shorter and final install smaller. Only "Services" removal can make your system very slightly faster but then again removal of some services might make your computer slower so better know what you are doing (and better safe than sorry).

You can only see if the drivers are ok on a REAL hardware install, the fact it sees your HDD in virtual box is irrelevant. If you set CD as 1st boot device and removed the "press any key" message via nLite, you will always boot from cd and be caught in the loop you describe. You now need to press F12 at start and choose HDD as temporary boot device to see if install goes on, but it is beter to set cd to boot after HDD in your virtual machine setup. +Your ini file is not attached.

You need to have administrative rights, then you can install a LOCAL printer, on a TCP/IP port that is the IP adress of the printer (you need to "Create a new port"). You can ping the printer name to get it's IP or get it in the printer's properties ("Port" tab).

You can install Virtualbox and test ("boot" a virtual machine) your ISO with it, it will behave as a normal install (except for the drivers) and ask for previous version if needed. As for testing the Sata drivers, you can, of course, boot the cd before zeroing, to check if it sees your HDD.

No. You'll just be told that your install process does not see your hard drive and thus cannot do anything to it. No repartitionning, no formatting, no install, no change.

What does the label say ? Windows XP does fit on "only one disc". There might be confusion between the actual "Service Pack 3" update (~316 MBytes) and the updated (to SP3) OS install disk (more than 600 MBytes). If the disk is bootable and contains an i386 folder, it is likely to be OK. Now for your error, .. no clue.

1. All devices are installed when there are no question marks left in device manager. If the driver is latest version, thet is more difficult to know. If the driverpacks include the latest drivers for your hardware , depends how new your hardware is. NLite does copy the files that are needed by the driver installation (I believe the file names are read from the inf file), so no need to copy them manually. nLite does include the driver, so no need to launch setup.exe. Justy point nLite to the inf file. It is possible that you miss some fancy functions of your hardware if "only" including the bare driver, in which case you might try to include additional software in an addon. -> see the "Application Addons" forum for your question about making one if needed. 2. leave nLite to integrate inf files or txtsetup.oem files as starting from a modified disk might get you in trouble. 3-4-5-6, if not sure, leave it alone, nLite then keeps Microsoft defaults (or at least from the cd you provide). Other users may comment further on this. Lots of options are interresting when you plan to use the same install disk a lot of times on your machine or for experimenting, but it is often easier (less headache and time consuming) to leave things as is and to bring a one time correction once Windows is installed.

I have no experience at all with that but as nobody answers, you could try My link.

I guess the tool to use depends on the format you start with (what sort of files).

That's all I could find yesterday, not very helpfull unless you do overclock your board. Are you 100% sure you're loading the good drivers ? Is it a new board or are you reinstalling after having used it without problem for a while? What if you install Windows 7 does it boot without error ?