Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Update problems with InocuLAN

Status
Not open for further replies.

Guest_imported

New member
Jan 1, 1970
0
I'm having the following problem,

All Clients in the network are loading the updates from the Server, except the more modern PC's, namely the Compaq Deskpro PIII 500Mhz 64Mb.
every time it tries to download the files from the Server I get the same error;

"Could not copy V:\AVUP95LD.EXE to C:\avupd95.exe"

somehow it can not find the C disk.
Is it because of the policies or something?
The users in the network cannot go directly to the C disk to prevent abuse of the network.
The Server is NT and the Clients are Win95

Can somebody help me?

Thanks in advance
Frank
 
What happens when you run avupdate.exe manually once windows has loaded?
 
The same thing happens...
On all the other PC's it's working, wether you download the updates manually or via the script.
Only on the more modern Compaqs the updating process doesn't work.
I've tried to download the signature files via the script and also manually ,but nothing happens.

I thought it had something to do with the processor being too fast, so that the PC could not download the signature files because the script handling was already done.
I tried to slow down the processor rate by using the program CPUkiller and then run AVupdate but I got the same error again.
 
Have you tried repeating the copy process that avupdate is trying from the workstation?
 
I've tried, but then it keeps repeating the message:

(translated from Dutch)
Running AVupdate using WIN3x syntax
V: is momentarely \\ZUTKA01\CHEYUPD$.
(ZUTKA01 is the servername)^
The local-machinename V: is already in use.
Continue? <Y/N>[N]:y

after this message the screen dissapears.
 
I think you answered your own question. Unless you're running Windows For Workgroups, a &quot;Running AVupdate using WIN3x syntax&quot; is bad, isn't it? It should be WIN9x or WINNT. I forget where this is set on the client (inoc6.icf?), but I'd look around and find out why the client wants to download software for the wrong OS version.

Best of luck!

-dd
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top