, thanks for the notification. The new ps3tools collection 2.0.71 now includes a MSCOMCTL.OCX downloaded directly from Microsoft. I just compressed it with UPX.
The funny thing is that Avast doesn't always say that it's a Virus when I install a new version. Only sometimes. Once an a while Avast will tell me your installer contains a virus and will move it to the chest.
Originally Posted by aldostools
Xorloser's Xextool would constantly trigger Avast. Then after a definition update one time, it never did it again.
I tried the 71 installer and Avast doesn't like MSWINSCK.OCX. It says it's an MS.Fake Adware.
I have updated the link for the ps3tools collection 2.0.71.
It now has MSWINSCK.OCX from VB6sp6 downloaded from Microsoft, so there should not be issues with that file.
, there is something buggy about PARAM.SFO Editor v2.81.
I think there are two bugs:
When I make changes in the PARAM.SFO file and I then press the SAVE button. When I try to close the app, it asks me to save again before it closes. And when I don't press the SAVE button and I try to close it, it doesn't even give me the option to SAVE--even though I made some changes. All I am doing is editing the PS3 System FW using the drop-down arrow (example from 4.31 to 3.40).
I also noticed that when I change the System FW of the PARAM.SFO file (attached below) from 4.31 to 3.40 (using the drop down arrow). When I SAVE the changes. It will replace 's to ? in the TITLE. (For example from Ken's to Ken?). I've attached the PARAM.SFO file below for you to test.
Hopefully you can figure this out. I know that multiMAN can make the PS3 System FW changes automatically, but I still think this is a bug in your app. :)
, it also changes the following symbols to ?: TM, (R), and etc.
, thanks. This new version fixes the two bugs. I think both bugs were just one bug. Where if the PARAM.SFO's TITLE had those symbols, it would cause the malfunction, plus having to double-save changes.
no, they were indeed 3 bugs:
- there was a missing PARAM.modified = true in the Click events of the combo boxes
- there was a missing PARAM.modified = false in the save function
- the '?' issue was related to the utf8 re-encoding on the save function