CJ Greiner

Those are some great links & good info. I'll try them out -- I'll let you know what I end up using. Thanks,

Thanks redsleeves -- I'll have to see if there's a useful way to implement that code. ______________ I've already taken a look at the timeout method -- and I like it for some of our computers where I'm pretty sure the users who leave it locked aren't working on anything important. In that case, it could time out at 30 minutes and log off any time without much consequence. For the ones that I only want to log off after their shift, it gets a little harder. We're on rotating shifts, so I can't really assign users to shifts then log them off on a timer after their shift. I could probably go into more sophisticated logging that tracks their most recent login activity and deduces what shift they're on, then timeout after the end of their shift... OR, if we can figure out how to use a key combination that wouldn't force the computer to the login screen, but instead trigger the code to log off the computer, then we'd be all set! Thanks,

Thanks for the reply... perhaps I should be more clear: We want to maintain our individual logins and the associated tracking and security associated with them. We do have some computers with shared usernames/passwords, but those are strictly non-networked and for use as Data Entry terminals for our equipment. What we're hoping to do is to add a component to our regular monitoring and shortcuts software that will allow us to "soften the blow" of having to kill power to the machine just to be able to use it again. Pushing the power button to perform a soft shutdown only works on a small number of our machines. It's not as good as just forcing a logoff, but it's better than the hard shutdown that most of our machines have to endure. We try to get users to log off every time they leave the computer, but there are those that forget... and thus the reason for my original request. I was hoping that maybe someone had worked on something like this, and I just wasn't able to find it using the forum search... Thanks,

I'm guessing that others have been in this situation too, and have probably already written programs to accomplish this: We have shared computers at work and when the previous shift leaves, they sometimes forget to log off and the screensaver leaves the computer locked. Holding down the "off" button to kill the computer's power isn't a very good way to get control of the computer... That seems like a good way to end up with a corrupted hard drive. I already have scripts on these computers for other purposes... I'd love to add a section of code that monitors for a key combination while the screensaver is running, and then log off the user smoothly so the next shift can log on. Thoughts? Ideas? Already-posted scripts that I missed in my search? Thanks,

Hi -- sorry... I wasn't trying to nit-pick, I was trying to give you some help with this script, which in previous posts you had mentioned you were still working on and hadn't figured out the bugs yet such as how to get the preview to show. Ahhhh... and you're right: I've been using v3.2.2.0 I'm using a laptop at home, and a PC at work... and both computers compiled the program correctly once I made the previously mentioned changes. (you never want to request the system open a program over and over again until AutoIt sees it -- it did lock up both of the computers I tried it on.) I'll try it again with v3.2.10.0 - Thanks!

I've seen other folk's scripts for screensavers, but they have problems with the preview showing... does your program show a preview in the screensaver tab of display properties? Thanks,

Hi Guys, Thanks for posting your screensaver script -- it's great! I'm not able to install fonts on the work computer, but the "Symbol" font makes it look pretty cool. The computer at work isn't very fast, so I'm not seeing the strings of symbols waterfalling down the screen like the movie, but it still has at least a nice basic Matrix effect. ___________ There's a problem with the script. It's in the section where you're trying to do the preview. You put the following code inside a loop: While Not WinActive("[CLASS:#32770]", $SSP_Text) Run("rundll32.exe shell32.dll,Control_RunDLL desk.cpl,,1") If @error Then Return SetError(1) Sleep(1) WEndYikes! That tells the system to open window after window of the windows screensaver tab -- crashes the computer! You'd be better off doing something like this: Run("rundll32.exe shell32.dll,Control_RunDLL desk.cpl,,1") While Not WinActive("[CLASS:#32770]", $SSP_Text) If @error Then Return SetError(1) Sleep(1) WEndAt least it won't crash the computer. Also, there's a problem in this line: Local $sChooseColor = _ChooseColor(2, $sSetColor, 2, $GUI)There's one too many parameters... It should probably be: Local $sChooseColor = _ChooseColor(2, $sSetColor, 2)Was the $GUI needed for something? The preview doesn't seem to work on the XP computers I've tried this screensaver on... have you come up with a fix? Thanks!

So far, I haven't had any problems with the newly-recompiled versions of my programs. BUT: my company hasn't updated to a more-recently released antivirus definitions yet so I haven't been able to see if any of the AutoIT3 release files are still targeted. Is anyone else still having problems?

I'm glad you guys posted about this problem and took actions to fix it. I've used AutoIt to create a very useful program for our local guys in the office. While it's not an absolutely necessary program, it certainly helps to have it running... So this morning I showed up at work, and it was gone! Apparently the auto-scan that's run every week on our computers skipped right over quarantine and jumped to delete. It deleted the file I wrote, as well as several AutoIt installation and SciTe files. I don't have the full list, but it appeared as though every .exe in the "full download" for AutoIt was identified as a "downloader" by Symantec. (i.e. it thought they were programs that downloaded trojans/spyware from the 'net.) So, I went to the backup disc and re-compiled the file, but this time instead of "allow decompile", I chose a high compression with no decompile -- and that worked. It still wanted to delete my AutoIt .exe files, as well as a .bin file in the "toExe" directory. Hopefully this doesn't happen again anytime soon!