anyone loaded 4.8 onto XP/SP3 ?

[tedzap]

Hello,

This is not programming related, but if there is a problem between SP3 and ProComm I would think it general interest to the group. I thought someone here might have seen this or have ideas.

I have a customer who has picked up a new laptop that has XP/SP3 installed. He has tried several times to load ProComm 4.8 and it fails with three popups (listed below).

As of this time I don't have the ability to reproduce this situation, but working on that.

Thanks in advance,
-Ted


1st popup:
Unable to load iswinapi.dll

2nd popup:
General file transfer error. Please check your target location and try again.
Error number: -119
E:\PROCOMM PLUS\CD\
C:\Program Files\Symantec\Procomm Plus


3rd popup:
Failed to create Registry Key

 

[geirendre]

1. Is the user trying to install an Administrator on that PC?

2. Is the machine member of a Windows domian?

Have seen similar errors on PC's where policy restrictions
applied to the machine have prevented installation of programs,
and modifications to the registry.

 

[knob]

Ted, I just acquired an XP SP3 machine at work, will try to install there a little later. In the meantime, you might try copying the CD locally and see if you are able to have better luck. I have seen that work in a few instances.

http://www.aspectscripting.com

 

[knob]

I was able to install from CD on XP SP3 without any errors while logged in as an administrator, so I would investigate what user access level they have. My hunch is that they are not an administrator, which I believe is required to install Procomm (Power User may be able to squeak by, but I'm not sure about that).

http://www.aspectscripting.com

 

[tedzap]

Thanks for the replies. At least there probably isn't any fundamental problem with SP3.

He *is* a member of a domain, but has never run into any such security issues before. I am not "domain savvy", have never used them.

He also says the user he is installing from *does* have admin privileges.

The computer is a new dell laptop that came with XP/SP2. He then accepted the "critical updates" from uSoft which included SP3.

Thanks again. Any other ideas? I am going to recommend that he copy the CD over to his hard drive and install from there.

-Ted

 

[knob]

If he runs the User Accounts application in Control Panel, what group is his logon account a part of (this will be on the right of the dialog)?

http://www.aspectscripting.com

 

[tedzap]

Thanks. I shot him that question, he said he will let me know when he gets another look at it (hopefully tomorrow).

The salesman had already grabbed it and left the building.

 

[tedzap]

Hello, thought I would report back my findings in this matter.

The folks in question have a domain set up, and he was logging on as a domain user with administrative privileges. This is sufficient for him to load many software programs (such as office) but not ProComm. In order for him to load ProComm he had to come in as a laptop user with administrative privileges.

I am pretty much domain ignorant and didn't realize the difference. They have had this domain for over a year and had forgotten about the "other way" of loggin in.

Thanks for the help.

 

[x11tech]

Someone forgot to give the domain admins "local admin rights.

 

[barngdes]

I have a standalone PC running XP Home SP2 that has the identical problem with installation, as the only user on the system - admin priviledges assigned.

I have copied the files reported to be uncopied/missing to the Procomm directories (iswinapi.dll, pwutil32.dll & navsdk32.dll) with no change in the problem. I've installed Procomm on several other laptops with XP in the past with no issues (although they were all XP professional, as opposed to the home version).

Any suggestions?

 

[tedzap]

My problem ended up being related to domain privileges. Doesn't sound like this would be applicable to yours.

Best,
-Ted

 

[Kyle753]

I have the exact same issue. Windows XP pro (SP3) unable to load iswinapi.dll. I have full admin rights. I have also installed this application on numerous PCs including XP Pro and XP home with no issue. Not sure what has changed. Any help would be greatly appreciated

 

[knob]

I would try turning off any virus scanners that might be installed during the installation and see if that helps. navsdk.dll sounds like something from Norton Anti-Virus and is not present on my machine, while pwutil32.dll is a Procomm-specific machine. I would also try copying the CD locally and run the install from there to see if that helps.

Kyle753, is your PC part of a domain or a standalone machine?

http://www.aspectscripting.com

 

[barngdes]

Problem solved.

I fully deintalled Norton Internet Security, purged all partially installed aspects of Procomm, rebooted and reinstalled Procomm after copying CD to the hard drive directory. Not 100% sure if the CD copy was significant to the resolution, but Procomm is installed and am back to test & deployment.

Thank you!

 

[Kyle753]

Thanks for your help. i went to MSCONFIG and restarted using minimal drivers etc.. without Norton running and i installed Procomm just fine. I'm back up and running. thanks.