XP and Drive Image v7

[Bob Johns]

I have two home computers using XP Pro networked via a Linksys router.


I share files, printers, and a broadband connection between the two, and
having been doing so for several months without problem.


This morning I installed Drive Image v7, and in the process it installed
..Net Framework. The install stated that .Net Framework had to be
installed in order for DI to work.


The problem I now have is although the computer that has DI installed on
can be seen by the other, the second machine cannot access files any
longer. The computer that has DI installed can see and transfer files to
the second without problems. There is a message that states something
like "check to see if you have administrator rights", and "not enough
server memory".


I took a look at the PowerQuest, and .NET sites but could not find any
obvious solutions. I suspect that .NET Framework has added some
additional layers of security, but have no idea how to verify or change
any perimeters. Any suggestions appreciated.


B Johns
Guam U.S.A.

 

[Bob Johns]

I have two home computers using XP Pro networked via a Linksys router.


I share files, printers, and a broadband connection between the two,
and having been doing so for several months without problem.


This morning I installed Drive Image v7, and in the process it
installed .Net Framework. The install stated that .Net Framework had
to be installed in order for DI to work.


The problem I now have is although the computer that has DI installed
on can be seen by the other, the second machine cannot access files
any longer. The computer that has DI installed can see and transfer
files to the second without problems. There is a message that states
something like "check to see if you have administrator rights", and
"not enough server memory".


I took a look at the PowerQuest, and .NET sites but could not find
any obvious solutions. I suspect that .NET Framework has added some
additional layers of security, but have no idea how to verify or
change any perimeters. Any suggestions appreciated.


B Johns
Guam U.S.A.

Well I did a complete un-install of both .NET Framework and Drive Image.


Even at that I still got the "Not Accessible errors". I did a System
Restore, and all worked fine.


I then re-installed .NET Framework and tested the two systems. No
problem. Everything works fine.


I then re-installed DI and right away the same "Not Accessible" "Not
Enough Server Storage" errors. I then removed DI and after a reboot
still got the errors. I then did another System Restore and all worked
fine.


This is definitely an issue with DI v7 and not .NET Framework as I
originally thought. The new version of DI uses something it calls V2i
Protector which is probably the culprit.


I have sent out a couple of mails to PowerQuest but so far no response.
I am beginning to think this program has major problems.


I am testing it because I need to be able to restore from an external
Firewire HD that I use to backup both systems, as well as my Notebook. I
tried the demo of TrueImage but it had problems seeing the external
Firewire when booting from the recovery CD. I am working with their
TechSupport to resolve the issue.


It is strange I purchased DI (at a discount since I own DI v6) and yet I
can't get timely TechSupport, yet Acronis is trying to help although I am
only testing their demo.


B Johns

 

[Sarge]

I am testing it because I need to be able to restore from an external
Firewire HD that I use to backup both systems, as well as my Notebook.
I tried the demo of TrueImage but it had problems seeing the external
Firewire when booting from the recovery CD. I am working with their
TechSupport to resolve the issue.

Take a look a Ghost 2003, it should be able to do what you want.

It is strange I purchased DI (at a discount since I own DI v6) and yet I
can't get timely TechSupport, yet Acronis is trying to help although I am
only testing their demo.

Powerquest isn't famous for customer service. :-(

 

[R. McCarty]

Since PowerQuest is being bought by Symantec, you can expect
Drive Image to be replaced by Ghost. Partition Magic is probably
the single reason that Symantec acquired them.( No comparable
product in their line-up.)

 

[MAG]

Since PowerQuest is being bought by Symantec, you can expect
Drive Image to be replaced by Ghost. Partition Magic is probably
the single reason that Symantec acquired them.( No comparable
product in their line-up.)

I wouldn't be too sure of them obsoleting Drive Image. I've used both DI
and Ghost, and find Drive Image to be the superior product by far. It
would be crazy for them to throw it out. Hopefully they will dump Ghost
instead.

Marc

 

[Bob Johns]

Since PowerQuest is being bought by Symantec, you can expect
Drive Image to be replaced by Ghost. Partition Magic is probably
the single reason that Symantec acquired them.( No comparable
product in their line-up.)

Just to let the group members know that PowerQuest did come up with a
solution to the problem I was experiencing after installing Drive Image
v7.


To recall I was getting "Drive Not Accessible" "Not Enough Server
Memory" errors when trying to access WorkGroup computers on my small home
network.


The issue was resolved by doing the following:


The error "Not Enough Server Storage is available to process this
command" might be reported after you install Drive Image 7.0, and
subsequently you might be unable to connect to the server/computer. This
occurs because the server's configuration for I/O Request Packets (IRPs)
is too low. The problem occurs on Windows 2000.


Fix: You can correct the problem by increasing the registry value and
restarting the server. The registry key you need to edit is:


HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer
\Parameters\IRPStackSize


NOTE: The key name "IRPStackSize" is case-sensitive.


If no DWord value is present, use the following defaults:


Windows 2000: 0xf (15)


maximum values are:
Windows 2000 Service Pack 2: 0x32(50)


On servers with a large number of file system drivers (antivirus, open
file backup, etc.), the IRPstacksize value may have to be increased to
resolve the issue. On Windows 2000, try setting it to 0x14 (20).


For more information, see Microsoft Knowledge Base Article Q106167 or
Q177078. If NetWare users in particular are affected, see Article
Q299783.


I had to use the value of (20) as 15 did not work. Now all is well.


B Johns
Guam U.S.A.