[clue-tech] upgrade question

[Charles Oriez]

At 09:27 PM 12/26/2004, skipworthy wrote:
>\
>FAR FAR BE IT FROM ME to defend Microsoft, but c'mon...
>
>David Anselmi wrote:
>
>>
>>You can't move your Win2k install to a new motherboard.  Period, end of 
>>sentence, been there, done that.  The reason is that Windows uses a 
>>driver that is chipset specific to your IDE controller.  Once you go to a 
>>new controller Windows will choke when it loads the wrong driver (it will 
>>"boot" but then will give you a stop 0x7B).  I have seen registry hacks 
>>you can use to change the driver but they're ugly (even as registry hacks go).
>
>Actually, I have done this very thing many times with *very few* issues at 
>all: Though I agree that it may not be a good idea ( in fact I wouldn't 
>recommend ti for a whole list of reasons), and it probably won't be real 
>stable,  but it has a 99% chance of success: and if the machine will get 
>past POST, and Win2k will boot and recognize the drive, you're more or 
>less home free. Again, I agree that its better to get the newer drives 
>going, but even a 'chipset specific' driver is unlikely to cause a stop 
>error, and its even less likely that a 'registry hack' will make that much 
>difference.


i have enough machines on my network that i am inclined to drop the 
idea.  if i limit that box to data storage and the suse OS the slowness of 
windoze wont be an issue

tnx for the feedback though