Text 3539, 60 rader
Skriven 2012-09-07 15:28:05 av mark lewis (1:3634/12.0)
   Kommentar till text 3529 av Roy Witt (1:387/22)
Ärende: Dupes
=============
 RW>> I'll let you know when I replace that file and what happens next.

 ml> a corrupt file is also a possibility but i've rarely ever found such
 ml> to be true... especially with a proper shutdown and such... if the
 ml> file was good on the last reboot, what happened in the mean time that
 ml> might corrupt it?

 RW> A full drive that didn't have room enough to defrag properly. 

i've gotten that numerous times on my w2k system... i would then generally go
clean out all the left over crap in the temp directories and definitely all the
crap in the internet cache... even though i never use IE, there are programs
that do use the dlls that make it and those are coded to use those cache
directories, too...

 RW> I got the warning ahead of time that I should delete some files to 
 RW> make room, but I ignored that warning 

i did all the time, too... other than the above cleanup... it just took longer
to run the defrag and also couldn't defrag larger files... so when i ran
defrag, it was a manual operation and i ran it numerous times and always looked
at the ending log to see what files were split into multiple parts... some of
those weren't needed either so they also went into the bitbucket before the
next defrag run... i think defrag wants 5% or 10% of the drive to be free for
it to do its work...

 RW> because I didn't have any intention of keeping W2k, while planning 
 RW> an eventual switch to XP. As it was, I just had to change up the 
 RW> plan and install XP on the backup drive (which is much faster and 
 RW> has 5 drives partitioned on it - one with a primary boot sector). 

i doubt that any of our machines will ever see XP... none ever saw ME or NT,
either ;)

 ml> i've seen NT installed to another directory on an existing system...
 ml> then that new install's registery editor was used to open the hive on
 ml> the broken install in the other directory... in this particular case,
 ml> we knew exactly what we were after in the hive to switch back to what
 ml> it had been changed to... you should be able to do this same
 ml> procedure... just do a plain install to a different directory and do
 ml> not gather up any of the previous software... consider this
 ml> installation as a maintence install akin to OS/2's maintence boot
 ml> item...

 RW> I'd rather not bother. If it won't come back, then it will be
 RW> cleaned and a new OS installed...W2k is no longer supported and
 RW> there are no programs installed on that drive that I will miss.

in the situation i spoke of above, recovery was the only option... espcially
considering the data on the machine which had already been moved twice during
the install and upgrade process to the whole new system... the other machines
had already been tasked with other work and were not available any more in
their original condition or form...

as it was, in that situation, there was only one item in one registry entry
that needed to be changed from a 0 to a 1 or the other way around...

)\/(ark

 * Origin:  (1:3634/12)