Partition Magic 8: "Can't create scripts"

[William W. Plummer]

I would like to understand what I did to one of my systems. I believe
I mangled permissions somehow. I got things back close to normal but
when I tried to install PM8, I get the error. Can someone tell me where
PM Install is trying to write the scripts? Could part of the registry
be protected? How do I reset registry protections back to normal?

 

[sgopus]

What is the error?
also be advised PM is not part of windows, and you could receive better help
by going to their web site and asking this
question in their groups...

 

[William W. Plummer]

What is the error?
also be advised PM is not part of windows, and you could receive better help
by going to their web site and asking this
question in their groups...

The problem is caused by something wrong in Win2K. The error in
Partition Magic is only a manifestation.

 

[sgopus]

The question still stands, what is the error??

The problem is caused by something wrong in Win2K. The error in
Partition Magic is only a manifestation.

 

[William W. Plummer]

The question still stands, what is the error??

The exact error is "1607: Unable to install InstallShield Scripting
Runtime."

 

[sgopus]

Here are some possible causes


Cause
This issue occurs on some systems depending on the system configuration and
privileges set for the user. Listed below are some common causes of this
error message:

1.. The user does not have administrative privileges on the machine. This
pertains to Windows NT, 2000, or XP machines.

2.. The ALLUSERS property is not set appropriately for the IsScript.msi
file. This is only true for the installation of Express 3.54 itself. Express
3.54 setup is based on InstallScript, leading to this error message.

3.. Permissions are not set appropriately on the Installer folder in the
Windows folder.

4.. An older version of InstallShield Express 3.x is installed on the
machine, and the older version fails to uninstall properly. This usually
happens when upgrading Express from an older version to a newer one.

5.. Multiple instances of files Msiexec.exe or IDriver.exe may be running
in memory.

6.. The Windows Installer Service may not be properly installed or
configured on the machine.

7.. The installation is trying to remove a file that is locked on the
machine. This issue generally occurs when setup is being removed using the
'Remove' option of the Add Remove Programs applet on Windows XP, 2000, or
ME.
Check this link, for possible solutions :

Next time, less argue, and more details, I hope this helps!

http://support.installshield.com/kb/view.asp??pcode=ALL&articleid=Q107094

 

[William W. Plummer]

Here are some possible causes


Cause
This issue occurs on some systems depending on the system configuration and
privileges set for the user. Listed below are some common causes of this
error message:

1.. The user does not have administrative privileges on the machine. This
pertains to Windows NT, 2000, or XP machines.

2.. The ALLUSERS property is not set appropriately for the IsScript.msi
file. This is only true for the installation of Express 3.54 itself. Express
3.54 setup is based on InstallScript, leading to this error message.

3.. Permissions are not set appropriately on the Installer folder in the
Windows folder.

4.. An older version of InstallShield Express 3.x is installed on the
machine, and the older version fails to uninstall properly. This usually
happens when upgrading Express from an older version to a newer one.

5.. Multiple instances of files Msiexec.exe or IDriver.exe may be running
in memory.

6.. The Windows Installer Service may not be properly installed or
configured on the machine.

7.. The installation is trying to remove a file that is locked on the
machine. This issue generally occurs when setup is being removed using the
'Remove' option of the Add Remove Programs applet on Windows XP, 2000, or
ME.
Check this link, for possible solutions :

Next time, less argue, and more details, I hope this helps!

http://support.installshield.com/kb/view.asp??pcode=ALL&articleid=Q107094

My problem centers around the security permissions on C:\WinNT\Install,
cited as a possible cause of error 1607 on the InstallShield.com site.

I cannot change the permissions because I don't have access, even though
I am in the Administrators group. I seem to remember that only the
Owner of a file or directory can change the permissions. I believe
"SYSTEM" should be the owner, but I can't change that either because I
set myself as the owner sometime ago. The next biggest hammer I can use
is SETACL from the Resource Kit. I'll try that later on. Thanks for
your help.