I think you are right with regard to the hardware portion. Hopefully we can figure something else out. To answer your question (in our arena), we have a Campus Agreement with M$ that includes getting us one campus key code thus activation is not required in the same fashion. At 03:00 PM 8/11/2003 -0400, you wrote: >Matt, > >It seems to me that a central premise of imaging is that the hardware must >be exact (or close enough that it will boot so you can repair minor >discrepancies, as you mentioned). > >If that's not the case, I wouldn't think you would be surprised. > >Looks like you'll have to create a new image for the new hardware. > >BTW, how does imaging work in these days of key codes and activation? > >Mark > > >-----Original Message----- >From: mswindowsxp-bounce@xxxxxxxxxxxxx >[mailto:mswindowsxp-bounce@xxxxxxxxxxxxx] On Behalf Of Matt Fowler >Sent: Monday, August 11, 2003 2:46 PM >To: mswindowsxp@xxxxxxxxxxxxx >Subject: [mswindowsxp] Imaging question > >Has anyone had a problem imaging Windows XP to a 2.4Ghz workstation? We get >a BSOD on boot before anything really happens. Once we do a CD repair >everything works normally. > >Thanks for any help. > > >Matt Fowler >LAN Specialist >(847)925-6113 >mfowler@xxxxxxxxxxxxxxx > >--- >Outgoing mail is certified Virus Free. >Checked by AVG anti-virus system (http://www.grisoft.com). >Version: 6.0.507 / Virus Database: 304 - Release Date: 8/4/2003 > > > > > > > > >================================== >To Unsubscribe, set digest or vacation >mode or view archives use the below link. > >http://thethin.net/winxplist.cfm Matt Fowler LAN Specialist (847)925-6113 mfowler@xxxxxxxxxxxxxxx ================================== To Unsubscribe, set digest or vacation mode or view archives use the below link. http://thethin.net/winxplist.cfm