the time i checked this (12 month ago) the problem was an official unresolvable bug.
its just a matter of loading the target chipset driver first.
sysprep with its pnpscan might help too, but you might loose something you didn't want.
I believe that if the HAL is ok (ACPI or noACPI) then you just have to have the chipset drivers in the right places.
looks like that the sysprep is a possible solution. here is the link about the tool and a corresponding error:
http://support.microsoft.com/default.aspx?scid=kb;en-us;257813
but all the "maybes" and "error codes" in the article are not very convincing to me. but thanks for the hint. maybe the next i will not replace the win2k with debian because installing linux is much easier/faster than a comparable win2k.
cya -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
