…is in the next SysAlive release candidate (rc3 for those keeping track).
Gotta thank Majick in the X10Hosting Offtopic IRC channel for this one: Emailed Notifications. I’m still ironing out a bug with it (I can’t get it to allow server authentication for ones that don’t support anonymous logins for sending emails) but otherwise it’s working fine. Sends updates every 15 minutes if there’s at least 1 server marked as Offline (to avoid spam it’s defaulting to Don’t Send Updates For Warnings – you don’t need to know when it might be down, you need to know when it IS down). Thanks again, Majick!
Also, for those who hate the X = Minimize To Tray fix I put in RC2, thank Sharky – it’s now a Confirm Close instead of minimize so if you hit X it’ll ask if you want it to close or not. Plus at the same time I found a way to make it NOT hang Windows when the system is shutting down – it used to abort the shutdown if it wasn’t closed by File>Exit or RightClick>Exit, which would mean as the OS shuts down the program would abort and essentially stop the shutdown. When I was looking for how to detect shutdown by that X, I found how to detect it by OS Shutdown as well, so if it’s being closed by the OS it’ll shut down normally. The log entry is a bit different though.
So that’s about it for now, just giving out a progress report while I get the last few known SA3 RC2 bugs ironed out before tossing out RC3. Stay frosty people!
Edit: Emailed Notification suggestion by Majick, added his name in the post.
So brilliant ol’ me decided to go and try coding an application to control/monitor certain enabled programs, such as SysAlive 3. The main bonus was supposed to be being able to check a certain webpage or file for a list of current MD5 hashes of all the supported apps (or at least their version numbers) in order to determine if updates were available or not.
I found a problem with that idea I’ll need to sort out though. It seems the way c# works, I need to have the process LAUNCHED from said monitoring program – I currently can’t find a way that lets the monitoring app run separate from the initial application. So rather than having SA3 running first then you run LWHQ Suite Updater, you’d have to run LWHQ Suite Updater and it’d proceed to launch SA3. Frankly that sucks so I’m going to be mucking about with this for sometime.
If you’ve got a way to make it so I can monitor SA3’s StandardInput, StandardOutput, and StandardError StreamReader/Writer’s without having to start the app from the updater, please register and drop in a comment (it’ll get stuck in a moderation queue but I’ll definitely read/approve it if it’s even SLIGHTLY useful).
But for now, I must go sell shoes. Later folks!
Good enough; PCAlive and the EmuLauncher are linked up again, they’re under Programming Bank on the left.
Honestly that’s all I’m doing for tonight; I’ll try to borrow my moms camera and take a picture of the arcade tanksticks externals and internals, just so theres another article I can post.
Hope everyone likes the new look, its a ton easier to navigate than Joomla was (for me at least) 