Archived from groups: microsoft.public.win2000.hardware,microsoft.public.win2000.file_system,microsoft.public.win2000.general (
More info?)
you can get around that issue by changing the path in the registry to this
key
Change from:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current
Version\Winlogon\Userinit:Reg_SZ:C:\WINNT\system32\userinit.exe
Change to:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current
Version\Winlogon\Userinit:Reg_SZ:userinit.exe
there is more information in this article
http://support.microsoft.com/default.aspx?scid=kb;en-us;249321&sd=tech
This is common after gohsting a drive or upgrading from a smaller drive to
another larger one. I would recomend making the change before switching
drive letters so you don't need to mess around with network conections. also
i think this article will shed some light on it too.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;223188
you should be able to piece the stuff together and get it working.
An alternative to this hassle might be to just install the os on a small
partition then do a rename the drive letter of the second partition to the
one he wan'ts to use (m:\) then you should be able to do another install to
that drive and because of the way 2000/xp asigns drive letters it should
continue to se the drive as m:\ or whatever you use. you might need to
modify the boot ini to bot to it. I'm not sure why he would need to have the
boot drive letter as m: though. there should be another way around it like
mounting the filesystem as another drive letter. I'm pretty sure windows
2000/xp lets you do this. I know it can be done in linux but i forget the
way to do it in windows. M aybe there is somethign with dynamic disks that
would allow it? i dunno
"Jetro" <ik9480@spam.rogers.com> wrote in message
news:OfRml33bEHA.2840@TK2MSFTNGP11.phx.gbl...
> Apparently this article should be re-written in more plain and layman
> language.
>
> It was quite surprised reading it at a glance - it's seemed too good to
be
> true and contradicted all the experience - until I found the warning
(sorry,
> I follow all the Murphy's laws
which clearly states "Do not use the
> procedure that is described in this article to change a drive on a
computer
> where the drive letter has not changed. If you do so, you may not be able
to
> start your operating system. Follow the procedure that is described in
this
> article only to recover from a drive letter change, not to change an
> existing computer drive to something else." This warning must be printed
in
> bold and largest point!
>
> I change the C: letter on XP box as described and after restart and logon
> attempt the nice warning popped up: "A problem is preventing Windows from
> accurately checking the license for this computer. ERROR 0x80090006."
> All-hackers mentor Jerold Schulman explains: "This problem is the result
of
> the hardware ID on the restored installation being different from the
> hardware hash calculated for the current hardware. To resolve this
problem,
> perform an in-place upgrade of Windows XP and reactivate the Windows XP
> license." Thank you very much, I was thinking, but I don't want no silly
> in-place upgrades and quickly returned the letter C: (maybe I deleted the
> value completely). As expected, the system's been shaken but didn't raise
a
> brow and came to life.
>
> Next victim was W2k installation just for redundancy. It wasn't
interesting
> already: after the first reboot I got infamous warning "No paging file" so
> it involved registry editing at HKLM\SYSTEM\CCS\Control\Session
> Manager\Memory Management, REG_MULTI_SIZE "PagingFiles", and after that
> logon got in the dead loop without any warning as predicted. I gave up.
>
>