So whose bright freakin’ idea was it to scrap my old XNA launcher and recode it from the ground up, AGAIN, just because they got a few ideas that simply don’t work with the old xml’s, the old layout, or pretty much anything that was part of the old system?
*points to self*
More after the break Read the rest of this entry »
I wasn’t able to get e-mail fully working for this one, although I did go and fix all the bugs I was informed about.
So yeah, V1 because of that. Frankly I’m not happy with this, but until I get the <explicitives censored for the sake of humanity> authentication working, email is useless – there are virtually no hosts that’ll allow sending of emails without a login/password. Helps prevent spammers and all that.
SysAlive 3 V1 Zip [Download]
Sysalive 3 V1 Installer [Download]
*WARNING:If downloaded before 11-20-08 at midnight CDT, installer says v1 but app says RC3. I updated installer, so it works now.
I’ll do what I can to get something useful done for this app, but at this point I’m running out of ideas for USEFUL things other than email. Maybe a help file, although the app is so bloody simple…
Vista Edit: Appears to run fine on vista 64bit; didn’t test 32, but I can’t see it having problems when it was designed and built for a 32bit os. If you have any problems, drop a comment, I get email notifications, and bugfixing for Vista is probably the last bit of work I’m doing on this app.
Just like the title says; I got myself Windows Server 2003 and it’s running just dandy-fine on the Enterprise Edition installer. Only hitch is .net 2.0 isn’t considered to be an update, so those who want to run it on WS2003 need to get .net 2.0 and install it manually.
Still working on the last few glitches that have popped up. Nothing big, I’m just trying my darndest to NOT have an RC with bugs if I can avoid them
Stay tuned!
…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!
Just cause I’m feeling generous. Click for bigger image on the second one.

What happens when the server dies?

The main UI - I know Last 5 Events shows 6+ in the window, screen was taken before I fixed the glitch.
I might just get this done soon ^_^
Edited 5am: configuration menu’s about half done (icons and sounds aren’t configurable yet, but the dialog’s face time, fade time, and fade speed are all configurable, along with the delay, timeout, and maximum alerts for the servers).
Features as of right now:
- Core is made of Awesome
- Tray icon has 4 graphics; one for normal, one as an alternate image for flashing, one for when there’s servers in warn status and one for when there’s servers in alert status.
- Saving and Loading is done and compatible with the old SysAlive files, minus a few useless things the other one stored (such as HC for an addon I never finished)
- Able to choose between ConnectOnly (the old SysAlive style) and HTTP (the New and Improved SysAlive style) on a server-by-server basis. HTTP will attempt to download the page served by the server and search for a <body tag; if it finds it, great, server’s online. If it doesn’t, it means one of two things: Either the webpage is throwing an error and it doesn’t have a fancy error page with a <body> tag in it, or the server’s down. Either way, SA3′ll mark it as dead since any good page shouldn’t be returning errors anyways.
- Annoying Sound Effects. Yes, I brought these back; nothing like being awoken out of a sound sleep to some of the loudest sound effects you want to be woken up with when a server is offline
So yeah, the to-do list still has some stuff on it that was considered “standard” in the old SysAlive (minimize to tray, automatically loading the Servers.XML on startup), but those are generally fairly easy to do. The help file for this on the other hand…Not so much.
*clippy!*Â Hit this plz: http://livewire90210.com/wordpress/tag/sysalive/ There are updates to the status of SysAlive 3, and that link will get you to all of them, including the latest release information.
For legacy/archive reasons, the rest of the post is here, but it is indeed available.
But seriously, I’m starting to love and hate Google all at the same time. Three hours of code got squashed by 30 seconds of copy/paste to make it do one notch better than it used to – in particular, it used to only be able to check if it could open a connection to a website.
Now it downloads the page that website serves, the theory being if it connects and is able to get the page, the server is not only able to accept connections, but is ALSO able to actually serve pages. I’ve seen x10’s (my paid hosting company) free servers do similar, where Apache is up and running but so bogged down or overloaded that it actually can’t serve pages anymore. SysAlive 2 would say it’s online, whereas SysAlive 3 would bail out and call it down or non-responsive.
No ETA on it yet though. I’ve still gotta do a bunch of things I took for granted on the original, namely the alert popups, sounds (which needed tweaking anyways), XML read/write, and some basic program settings, and minimize to tray…I should make a to-do list so I don’t actually miss anything.
And on the subject, why is it that I can’t code for ****? I’m having to spend lots of time just translating my own code from the old SysAlive to something with comments that I can actually use.
A REALLY old thing I put together in Game Maker. I almost feel embarassed for not doing it in c#, but I’m working on an XNA based c# version right now anyways.
For now, you’re stuck with this, and it’s attrocious at best – it’s a pain to add new things because it’s extremely specific on how it wants things.
If you want support on it you’re on your own but there are demo files included (DOESN’T INCLUDE ANY ROMS OR EMULATORS) to show where the files and parts go.
LauncherV2.zip [Download]
PCAlive is an older program I need to do a rewrite of VERY badly – it’s built on .net 3.5 which means it has a stability problem – it gets a mysterious error message every once in a while if you don’t have .net 3.5.Â
In any case though, the program’s simple – add the host/ip, port, and a name to display it as, push “Add 2 Active” and the program’ll let you know when it fails to connect to that system.
Here’s a small catch: the program doesn’t properly verify the server is actually -responding-. If it’s a webserver for instance, it might be able to connect but the webserver might have frozen or is under high load and can’t actually serve pages. If my rewrite goes according to plan (so don’t count on this ever happening) I’m going to try getting it set up so PCAlive can actually send a request to the system in question, and wait for a response.
For now though, here’s the link to the app. Tested on XP SP2 Pro but not on Vista cause I don’t have Vista.
Sysalive.zip [Download] OUTDATED; Look for SysAlive3’s latest releast in the Repository!
Source used to be available on request, but at the moment I’m keeping it close to the vest – it’s not anything Google couldn’t help you do over