Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

64bit Reg-Keys werden mit UNWISE32.exe nicht gelöscht

Created: 04 Nov 2013 | 3 comments

Hallo,

ich habe unter WPS 8.0 MR1 im WiseScript Editor und unter AdminStudio for Symantec (11.5) im WiseScript Package Editor folgendes getestet:

Installieren eines Reg-Keys im 64bit Zweig.

Das anschieißende Uninstall per UNWISE32.exe versucht aber, den Reg-Key im 32bit Zweig zu löschen.

Im Dialogfeld für "Edit Registry" oder im WSE-Quelltext ist ein Kennzeichen für 64bit gesetzt.

Im Logfile unterscheiden sich die erstellten 32bit- und 64bit-Reg-Keys nicht. Es gibt kein Kennzeichen für 64bit.

Beispiel:

item: Add Text to INSTALL.LOG
  Text=***   32bit Zweig
end
item: Edit Registry
  item: Key
    Key=Software\_wise_test\32bit
    New Value=soll nach 32bit
    Value Name=Test
    Root=2
  end
end
item: Add Text to INSTALL.LOG
  Text=***   64bit Zweig
end
item: Edit Registry
  item: Key
    Key=Software\_wise_test\64bit
    New Value=soll nach 64bit
    New Value=
    Value Name=test
    Root=2
    x64 Support=1
  end
end

 

Im Logfile:

***   32bit Zweig
RegDB Key: Software\_wise_test\32bit
RegDB Val: soll nach 32bit
RegDB Name: Test
RegDB Root: 2
***   64bit Zweig
RegDB Key: Software\_wise_test\64bit
RegDB Val: soll nach 64bit
RegDB Name: test
RegDB Root: 2
 

 

Woher soll dann UNWISE32.EXE unterscheiden können, in welchem Zweig gelöscht werden soll?

Rolf307

Operating Systems:

Comments 3 CommentsJump to latest comment

Rolf307's picture

Hi,
let's try again in English:

I tested the following with WPS 8.0 MR1 / WiseScript Editor and with AdminStudio for Symantec (11.5) / WiseScript Package Editor with the same results:

Installing a Reg-Keys in the 64bit tree. This works fine.

After this I tried to uninstall the package via UNWISE32.exe, but UNWISE32.EXE tried to delete the Reg-Key in the 32bit tree instead of 64bit.

In the WSE-Dialog "Edit Registry" and in the WSE-Source there is a tag for 64bit "x64 Support=1".

But in the logfile there is no difference between 32bit- und 64bit-Reg-Keys.

Example:

-------------------------------------------------
item: Add Text to INSTALL.LOG
Text=*** 32bit Zweig
end
item: Edit Registry
item: Key
Key=Software\_wise_test\32bit
New Value=soll nach 32bit
Value Name=Test
Root=2
end
end
item: Add Text to INSTALL.LOG
Text=*** 64bit Zweig
end
item: Edit Registry
item: Key
Key=Software\_wise_test\64bit
New Value=soll nach 64bit
New Value=
Value Name=test
Root=2
x64 Support=1 <========
end
end
-------------------------------------------------

In the Logfile:
-------------------------------------------------
*** 32bit Zweig
RegDB Key: Software\_wise_test\32bit
RegDB Val: soll nach 32bit
RegDB Name: Test
RegDB Root: 2
*** 64bit Zweig
RegDB Key: Software\_wise_test\64bit
RegDB Val: soll nach 64bit
RegDB Name: test
RegDB Root: 2
-------------------------------------------------

How should UNWISE32.EXE be able to recognize, weather it is a 32bit or 64bit tree?

Rolf307

EdT's picture

The Wisescript 64 bit support in MR1 came with a heap of bugs and this is just one of them. It would appear that the Flexera guys have not done anything significant to the Wisescript code before bolting it onto their Adminstudio product, so there are still multiple bugs in the product.

I had a long debate with the Wise product management when the original draft spec for adding 64 bit support to Wisescript was given to me to review, as there was very little in there of any benefit to packagers. Some additional features did get added but fundamentally Wisescript is a 32 bit product and until someone actually recodes it as a true 64 bit product, it is going to exhibit many limitations. I don't see that happening as there is not enough market interest to justify the development costs.

If you want to implement some form of uninstall with Wisescript then you are going to have to get creative and run an "uninstaller" program which will overwrite existing 64 bit keys with null values, or whatever is appropriate, and then trigger an unwise32.exe call to remove files.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

ekarlw's picture

I found this "Point Fix" that *may* address your problem - but it may undo other fixes which is my biggest complaint.

There are multiple 'point fixes' that replace the WISE0132.dll but NONE are cummulative, they all appear to start with the same broken baseline .dll and fix only that one issue - I have yet to find a rollup hotfix for this critical .dll.

Another desireable fix is the file copy using wildcards within WiseScript, but this also requires 'swapping' the WISE0132.dll

So my question to all is "do you know of any Hot fix / Point fix roll-up releases for WPS 8.0 R1?