Re: Reinstallation erases all?

Tech-Archive recommends: Fix windows errors by optimizing your registry

"Anton" <nosp@xxxxx> skrev i meddelandet news:...
"John John (MVP)" <audetweld@xxxxxxxxxxx> skrev i meddelandet
news:OasZXlotIHA.552@xxxxxxxxxxxxxxxxxxxxxxx
Anton wrote:

John John (MVP)" <audetweld@xxxxxxxxxxx> skrev i meddelandet
news:ee9VC0htIHA.1240@xxxxxxxxxxxxxxxxxxxxxxx

How about copying i386 over to the right part. and how?

All that hal.dll business points to the boot.ini file being incorrect
or
the partitions being damaged. Read here:

Error message: "Windows could not start because of a computer disk
hardware configuration problem"
http://support.microsoft.com/kb/314477/en-us

"Invalid Boot.ini" or "Windows could not start" error messages when
you
start your computer
http://support.microsoft.com/kb/330184/en-us

Error message in Windows XP SP2: "Windows could not start because the
following file is missing or corrupt. Windows\System32\Hal.dll"
http://support.microsoft.com/kb/945380/en-us


Thanks John for your help, I got a bit confused when most is about XP,
isnt
there any specifics for W2 or is that for w2000 help group?

Most of the above information also applies to Windows 2000, the startup
routine on these two operating systems are the same. If you truly
believe that the Windows 2000 hal.dll is damaged then see here:

How to Troubleshoot Windows 2000 Hardware Abstraction Layer Issues
http://support.microsoft.com/kb/237556/


Very longs lists what to do in that one.


I saw my W2 doesnt have any i386, can it damage trying to copy it from
another part?

The newest i386 folder would be in C:\WINNT\ServicePackFiles\i386, if
the installation had service packs applied after the installation you
should get files from the i386 folder shipped with the last service pack
that you installed. However, that is almost completely irrelevant, you
don't need this folder to start or run Windows 2000, the folder is only
an archive, it isn't needed to run Windows. Earlier you said that you
ran bootcfg but that it couldn't find the installations, that was when
some of your partitions were hidden, did you try it again after you
unhid the partitions?

As I recall XP was in cfg before, now its gone but all W2s are there.
W2 starter doesnt have any i386, doesnt it need any at all?

I have it in other W2s on that disk to copy what we need, if it works.

Think I'll try to copy/expand some. If it doesnt work I'll move it over to
slave in this working CP where install r works. Any better ideas?


PS Can anythning be damaged if I can suceed copying over i 386?


.

Relevant Pages

  • Re: Build Failed Message
    ... But seriously, do a complete re-install of your machine, or buy VMWARE. ... because there is still something wrong with your installation. ... I received no build.log file in the C:\WINCE600 folder. ... Windows CE 6.0 Platform Builder ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Build Failed Message
    ... you should (take a look at my blog for more info on cloning). ... The obvious solution to your problem is a reinstall of the entire machine, because there is still something wrong with your installation. ... I received no build.log file in the C:\WINCE600 folder. ... Windows CE 6.0 Platform Builder ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Windows XP & new motherboard
    ... But Windows 2000 and XP mostly just ... > buy or borrow a true installation XP CD. ... > some of the apps that came with the system. ... > 4) Enter "cd olddrive" to switch to the new folder ...
    (microsoft.public.windowsxp.general)
  • Re: Users all mixed up after reinstall: How to clean up?
    ... It appears that your original installation was an upgrade from Windows 98. ... That's why you have a Windows system folder and all the new users had some sort ... log on as Administrator then go to Control Panel> Users ...
    (microsoft.public.win2000.general)
  • Re: Clean reinstall getting dirtier each attempt?
    ... The 8MB of unallocated space is put there by Windows in case ... drive had a small first partition, 39MB, and a large second ... ended up installing it right back into the Windows folder ... And since it was the latest installation it became the ...
    (microsoft.public.windowsxp.help_and_support)