8 replies to this topic

[Anthony A]

SAS has recently released an update to 3.5. The winapp2.ini for SAS is no longer working. That is because the logs for SAS are now kept in C/Documents and Settings/user name/application data/SAS/logs folder. As you can see with this winapp2.ini entry they used to be kept in the C/programs/ SAS/ Logs.

[SUPERAntiSpyware (Logs)]
LangSecRef=3024
Detect=HKLM\Software\SUPERAntiSpyware.com\SUPERAntiSpyware
Default=True
FileKey1=%ProgramFiles%\SUPERAntiSpyware\Logs|*.log

[TwistedMetal]

I got SUPERAntiSpyware and didn't even notice that. I will be releasing a new update sometime tonight, it will be fixed.

[Anthony A]

TwistedMetal, on Jan 25 2007, 06:24 PM, said:

I got SUPERAntiSpyware and didn't even notice that. I will be releasing a new update sometime tonight, it will be fixed.

Thank You

[Andavari]

This actually takes care of the new SAS version:

Edit: Screw it, the forum is messing up the quote and the code.

[TwistedMetal]

Quote

I am quoting

I am making a codebox

[Andavari]

Duh, yeah that works.
What I was talking about was when posting the actual cleaning routine it was bunching the LangSecRef up next to the entry name, there wasn't anything I could do to fix it.

[TwistedMetal]

I was making sure, the Forums have been really screwed up lately.

[Anthony A]

Whats the latest with this?

[TwistedMetal]

Well, everything didn't go as planned. I was going to add several new entries to the winapp2.ini and release it, but... Well, I can't explain it, just yet.

I am going to release it today, it will be a small update with only a few entries.