XP Home & Drive Image 7

  • Thread starter Thread starter Shooter
  • Start date Start date
S

Shooter

If this isn't the right group - a pointer in the right direction would be much appreciated.

I'm trying to back up an image of one critical content XP computer over my home network to another newer XP computer. The image file is supposed to go into a 'shared folder on the second computer.

The network seems to work fine, and I can create and delete a file in the shared folder intended to hold the image backup.

But Drive Image 7 keeps saying - 'The Media is write protected' - even if I try to produce an image file on the original computer.

I just don't get it - maybe it has something to do with accounts. I'm the admin on both computers.

Many thanks
 
-----Original Message-----
If this isn't the right group - a pointer in the right
Click to expand...
direction would be much appreciated.
I'm trying to back up an image of one critical content
Click to expand...
XP computer over my home network to another newer XP
computer. The image file is supposed to go into
a 'shared folder on the second computer.
The network seems to work fine, and I can create and
Click to expand...
delete a file in the shared folder intended to hold the
image backup.
But Drive Image 7 keeps saying - 'The Media is write
Click to expand...
protected' - even if I try to produce an image file on
the original computer.
I just don't get it - maybe it has something to do with
Click to expand...
accounts. I'm the admin on both computers.
 
I "dumped" drive image a long time ago because of problem(s) such as yours.
I purchased Acronis True Image and haven't had a problem imaging to CD, second drives or over to a network drive.
 
I'm doing _exactly_ the same as you. I didn't have the problem you mention
but I did have several others that you might see later. None were caused by
Drive Image!

Regards

Colin


Problem 1
========

Drive Image kept saying it didn't have permission to access the shared
folder... Here is my solution....

If you are sure you have set up your accounts and shares correctly but you
still can't access a machine over your LAN and you get either access
permission errors or "Not enough server storage" (or perhaps other
messages?) then his might be worth checking.

Look in the event log on the "server". This might be an ordinary PC in the
case of a home LAN, either way it's the PC hosting the share you are trying
to contact. See if there is an entry telling you the irpstacksize is too
small.

I believe this problems may be due to Norton Antivirus S/W...

Norton have this advisory (long URL may wrap to new line and need repair)

http://service1.symantec.com/suppor...88256d03005eb145?OpenDocument&src=bar_sch_nam

and Microsoft have this one..

http://support.microsoft.com/default.aspx?scid=kb;EN-US;106167

HOWEVER the above only mention the error message being "Not enough server
storage...". I found it can also give access permission errors (something
like "Access denied" or "Insufficient acesss", I can't remember exactly).
These are really confusing to someone trying to set up a home LAN.

Here is what I found...

irpstacksize = 11 (dec) causes access permission errors.

irpstacksize = 13/14 the error changed to "Not enough server storage" or
similar.

irpstacksize = 15 and my network shares now work fine.



Problem 2
========

Once I had fixed the above I found my backup would abort half way through
with a "Delayed Write Failure". This is tricky to explain. The problem seems
to occur because shared folders can cause excess network traffic. I read
somewhere that every time the content of a shared folder is changed messages
are sent to all computers/accounts that have access to the share (eg every
time Drive Image appends a byte or two of data to the backup multiple
messages are sent out and this slows down the LAN to the point that a "write
buffer" gets overwritten).

The fix for me was to restructure the folders I was using to hold backups
and "push the share down a level"....

Before...

I shared a folder called "Backups" on PC1 and arranged for PC1 to write to
subfolder "Backups\PC1" and PC2 to write to Backups\PC2 etc.

After...

I removed the share from "Backups" and shared Backups\PC2 only. (Backups\PC1
does not need to be shared).

This seems to have cured the problem.



If this isn't the right group - a pointer in the right direction would be
much appreciated.

I'm trying to back up an image of one critical content XP computer over my
home network to another newer XP computer. The image file is supposed to go
into a 'shared folder on the second computer.

The network seems to work fine, and I can create and delete a file in the
shared folder intended to hold the image backup.

But Drive Image 7 keeps saying - 'The Media is write protected' - even if I
try to produce an image file on the original computer.

I just don't get it - maybe it has something to do with accounts. I'm the
admin on both computers.

Many thanks
 
Many thanks - I've since found a number of solutions - so it's probably a
good idea to post them so that search engines can pick them up.

Here's for the SEs: Drive Image / DriveImage problems /

The 'media is write protected' error was caused in my case by my
misunderstanding of Drive Image's interface - it's not that intuitive. I
was trying to make my backup into a folder I had already created called
Backup. When I browsed to it and hit open, I was getting the 'media is
write protected' message.

This is because drive image was trying to write 'onto' the folder, rather
than 'into' it. And of course, all Win XP folders are read-only, they're
write protected. The trick is to tell Drive Image to make a new folder -
and then it works. Stupid, but simple (you can take that to refer either to
Drive Image or myself ;)

I then had problems retoring the image over my small network.

2 Tips:

1. The source and target XP computers *have* to have password protection in
place or it simply won't work for security reasons.

2. In my case, the first step in recovering the data across a network after
booting with Drive Image is to hit 'Utilities' then 'Map Network Drive' -
navigate to the folder, and then enter the username and password of the user
*on the computer where the data is stored*

Hit finish, and now you can navigate around the source computer using the
features on the main screen to your files.

Thirdly - Drive Image then caused the problem described below by Colin. It
caused the 'Not enough server
storage' errors on other computers on the network. Follow the MicroSoft
link in Colin's post below, and edit the registry. I changed the
IRPstacksize to 15 on my XP computer and it was fixed. Note that the fix
has to be done on the computer that can't be accessed - not on the computers
giving the errors.

Everything now works - but I have to say, I've been working with computers
for years and this all took me a day and a half to figure out. The
documentation provided with Drive Image is crap - it is detailed, but why
these simple points aren't made clear is a mystery. The faqs / support on
the site are also totally inadequate.

Although it is now working, if you haven't got a few hours to spare, or
you're not that computer literate - DON'T BUY DRIVE IMAGE 7
 
Thanks for the follow up.

I think you were a bit hard on DI 7. Have you tried to do the same thing
with Ghost? I've got both and prefer DI for easy of use. At least I can
schedule a backup with DI!
 
Back
Top