After giving up on the problem deleting recently emptied folders, I
tried to update the W2K installation. This failed with a fairly common
error message EOX..... the details of which I do not have access to
for reasons explained below. None of the MS site suggestions allowed
the windows update to begin.

Assuming the W2K SP4 installation to be corrupt, I attempted to
perform an in-place upgrade, booting from the installation CD with the
correct raid drivers available during start-up. After failing to read
spxcoins.dl_ off the installation disk, or off a subsequent floppy
copy, the inplace upgrade stopped midway during final registry of
devices.

The spxcoins.dl_ is present on the install disk. The installation
program does not display the files name's '.dl_' type, when 'browsing'
for the 'missing' file.

This is repeated for any subsequent attempt to complete the upgrade.

As this is an ntfs installation on a raid device, I have no other
operating systems or hardware to retrieve data off the drive, and no
access to the second boot option WXP on the second raid hard drive,
while the first is non-compos mentis.

When I tried to install a temporary W2K OS in a drive mounted in an
IDE position, I got the same errors. The correct raid drivers are
loaded when booting from the installation CD, via floppy. Booting up
into W2K, I get the message that the install did not complete and a
run through of the same loop of missing .dl_file and stopped device
registry.

Any advice on:

1) completing the in-place upgrade
2) retreiving data
3) getting the temporary functional W2K OS installed on an IDE drive.

?

RL

The CD-Rom may be bad, the RAM could also be bad.


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"legg" wrote:
>
> After giving up on the problem deleting recently emptied folders, I
> tried to update the W2K installation. This failed with a fairly common
> error message EOX..... the details of which I do not have access to
> for reasons explained below. None of the MS site suggestions allowed
> the windows update to begin.
>
> Assuming the W2K SP4 installation to be corrupt, I attempted to
> perform an in-place upgrade, booting from the installation CD with the
> correct raid drivers available during start-up. After failing to read
> spxcoins.dl_ off the installation disk, or off a subsequent floppy
> copy, the inplace upgrade stopped midway during final registry of
> devices.
>
> The spxcoins.dl_ is present on the install disk. The installation
> program does not display the files name's '.dl_' type, when 'browsing'
> for the 'missing' file.
>
> This is repeated for any subsequent attempt to complete the upgrade.
>
> As this is an ntfs installation on a raid device, I have no other
> operating systems or hardware to retrieve data off the drive, and no
> access to the second boot option WXP on the second raid hard drive,
> while the first is non-compos mentis.
>
> When I tried to install a temporary W2K OS in a drive mounted in an
> IDE position, I got the same errors. The correct raid drivers are
> loaded when booting from the installation CD, via floppy. Booting up
> into W2K, I get the message that the install did not complete and a
> run through of the same loop of missing .dl_file and stopped device
> registry.
>
> Any advice on:
>
> 1) completing the in-place upgrade
> 2) retreiving data
> 3) getting the temporary functional W2K OS installed on an IDE drive.
>
> ?
>
> RL

On Thu, 20 Mar 2008 17:52:47 -0500, legg <(E-Mail Removed)> wrote:


>When I tried to install a temporary W2K OS in a drive mounted in an
>IDE position, I got the same errors. The correct raid drivers are
>loaded when booting from the installation CD, via floppy. Booting up
>into W2K, I get the message that the install did not complete and a
>run through of the same loop of missing .dl_file and stopped device
>registry.
>
>Any advice on:
>
>1) completing the in-place upgrade
>2) retreiving data
>3) getting the temporary functional W2K OS installed on an IDE drive.
>
Tried cloning a working W2K installation into the problematic position
using the generic Caldera DOS utility, but couldn't identify the
target partition, after W2K installer reformatted the NTFS space.
There were 'bios' partitions interspersed in the partitions detected,
and a large final partition was missing on a raid hard drive.

The installed OS partition I was trying to copy from became unreadable
when restored to its oroginal position.(in the older W98/W2K dual boot
system, only recently restored to function).

Finally succeeded with a clean install in the target position, losing
all applications installed in the previous months. After a few hours
and a few dozen reboots, it's updated to current SP4.

Not a very productive few days.

RL

Re: Problems deleting Folders
Make sure that you're logged on as an "Administrator", and that the
Properties / Security Settings give the Administrator "Full Control".
Additionally, in Windows 2000, a Deny setting for one User can affect all
users. Make sure that there are no Deny settings in place for any users.
If the Folder has the Attributes of "System", "Hidden" or "Read Only", then
you can't delete it until you remove these Attributes. You have to use
"Shell" (Command Prompt) to delete the Folder using the "rd" Command: "rd
FOLDER /s". First, type "attrib FOLDER" to get the attributes. If it shows
S or H or R, type "attrib FOLDER -s -h -r". Then you can remove it using
"rd" as previously mentioned. If you learn how to use Shell, you'll find
this much easier for managing files than Windows. I recently had a Spyware
Virus replicate itself hundreds of times over on my Hard Drive! Using Shell
I was able to find and delete all copies of the Virus in only about 3 hours.
If you send me an E-Mail ((E-Mail Removed)), I can send you the Batch
Commands I've written for backing up Files and protecting against accidental
deletes.

Re: Service Pack 4
After installing SP4, my FaxTalk Modem Software got screwed up, and after
uninstalling and re-installing it, it still didn't work. Windows Uninstall
didn't remove contents in the Registry. The FaxTalk Website provided info
for manually removing from the Registry, and after that it re-installed
correctly. SP4 seems to screw up some of the Registry contents -- requiring
them to be manually removed and re-installed.