XP Pro, and .NET Framework

  • Thread starter Thread starter Bob Johns
  • Start date Start date
B

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 it 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 this. Any
suggestions appreciated.

I removed both DI and .NET Framework but the problem
persisted.

I restored to an earlier date using ERS for XP/NT, and
all works fine. Of course I can no longer use either DI
or .NET Framework.

B Johns
Guam U.S.A.
 
-----Original Message-----
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 it 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 this. Any
suggestions appreciated.

I removed both DI and .NET Framework but the problem
persisted.

I restored to an earlier date using ERS for XP/NT, and
all works fine. Of course I can no longer use either DI
or .NET Framework.

B Johns
Guam U.S.A.
.
Click to expand...

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
 
Back
Top