Did you try quick format? Or vice versa and do a normal format?

Try this link, should tell you everything you wanted to know and then some:

http://www.msfn.org/board/index.php?showforum=157

I use this program and it seems to work pretty good, works on about 80-90% of hardware that supports booting from a USB device:

http://www.msfn.org/board/index.php?s=3 … pic=120444


My current disc setup is XP Home or Pro OEM SP3, slipstreamed using Siginet's RyanVM Integrator with Onepiece's EN-US Windows XP Post-SP3 All-in-One Update Pack (http://www.ryanvm.net/forum/viewtopic.php?t=6438) , then nlited the way I like (basically just the repetive stuff, time zone, language, etc and also removal of all extra keyboards and a few UI tweaks, a few addons like .NET All in One, MS signed themes and Fox It). After that, I run DP Base on my dir, then I run the Integrator again and use mr_smartepant's OEM activation addon (http://siginetsoftware.com/forum/showthread.php?t=541) and then I create my ISO w/ nLite. This is the ISO that I use when I run WinSetupFromUSB. And it works great, much faster than DVD.

Regarding the breaking of activation and product keys, I've been using mr_smartepant's Multi OEM Activation add on my Unattended install discs, it works like a charm.... I believe from some of the reading I've done over on Siginet's forum that tweaking of the addon could be done to have it run during sysprep mini setup and have the image correctly activated without worrying about a product key at all.

http://siginetsoftware.com/forum/showthread.php?t=541

http://siginetsoftware.com/forum/showthread.php?t=117

http://siginetsoftware.com/forum/showthread.php?t=276

I had exact same issue w/ building a Server 03 disk. It was Base 8.12.4. All latest driver packs. Clean source (OEM original - no SPs slipstreamed and nothing else integrated on disk). Did not finish loading text mode setup, gave same error as mentioned above.

5

(7 replies, posted in Other)

I'm assuming all these machines run XP... I think your better option would be to use Windows Steady State. That way instead of having to rebuild these machines all the time, whenever they reboot, they will be exactly as they were when they first started up. That will still allow your users to do whatever they need and install anything they want while saving you a huge amount of work.

6

(14 replies, posted in Universal Imaging)

My personal solution that I've started to go ahead w/ will be two cds: one OEM XP Home and one OEM XP Pro. They will both have multi-manufacturer OEM activation built in, have SP3 slipstreamed (then eventually RyanVM update packs when necessary) and have the Mass Storage and LAN drivers off the Driver Pack integrated on. On first boot, machines will map a drive to a network share, run DP_inst.exe and install whatever drivers it's missing, then reboot. On the 2nd reboot, they will install whatever applications I've decided on (probably AVG 8 Free, Spybot, OpenOffice). I think this approach will be easier to manage than my original plan of having a universal sysprep image.

Would it be possible to have the option added to BASE in an upcoming release where it would modify the original mass storage INFs to point to the additional ones? Is this is a feasible feature request? Or would it possibly cause conflicts?

HAH, ok I just wrote a post and went to submit it, then it said the server was too busy. Oh well, here goes again...

Would it be possible to skip the manual integration of the mass storage DP w/ sysprep if the mass storage DP was added to your original windows source using the KTD and text mode options? Is there any reason that this would not work?

Thanks

Yes, this is definitely possible. I work at a computer shop and I recently got this working. Using an nLited install CD w/ all the driver packs on it w/ the KTD option and RyanVm's latest update pack. It works awesome and is definitely worth the time to figure it out.

I actually used Virtual PC to create my image. After I had created my ISO (it was too big to burn on a CD because I also have some integrated applications on it) I installed XP. I did some other minor tweaking and when I was happy I sysprepped it and it seems to be working flawlessly. If you have any questions, post them here and I'll do my best to help you out.

Hey all, I found this site awhile ago and have played with the Driver Packs a bit, but until recently I haven't had the time to attempt what I ultimately wanted to do. I want to make a truly universal XP image that can be put on virtually any pc. Now from my understanding of how the Driver Packs work, I could make a Windows install CD w/ the DP integrated and the KTD option, install this on a base peice of hardware (well actually I'm using Virtual PC right now), sysprep it, then be able to deploy that image to various machines. This seems like a simpler process than what was being discussed a bit earlier in this thread, but since Bashrat is saying to do it that way, I'm curious if the way I want to do it will work fine. Any comments or suggestions would be appreciated guys, thanks a lot.