huggy59
Active Member
I have taken the plunge, sort of. I've got HS2 running under VMware on W2kPro. I did a clean install as I didn't have my old HS1.7 config around (that PC died again in May). Here's what I've found.
My inital install failed. I guess it installed .NET Framework, but it still errored out. I got the framework separately and installed it, things worked ok this time.
I still don't have TTS though. Not sure why. The Speaker app errors out when I start it. I'll have to look into that.
I initially didn't have the MDAC 2.8 install. HS2 corrupted the newly-created sample.mdb when it "saved" it on shutdown. Result: restarting HS2 hung because the database was corrupt. Nice. Why can't they just check for the right MDAC version BEFORE messing up the db?
I blew away the db and installed MDAC 2.8, then restarted HS2, it rebuilt the blank sample.mdb and off we went!
BUG: I added a few devices. Made a mistake and named two devices the same, HS2 didn't complain, but I couldn't see both devices on the web GUI. They were in the db, however. I renamed the one I could see, the other one came back, but then I had to modify it to make sure the db wasn't messed up. It LOOKS like it would be fairly easy to get the db screwed up by making this mistake again... not sure what the consequences would be. Maybe they need to enforce unique device names, or modify the web GUI so that it shows ALL devices... not sure what the issue is here but I have some ideas.
BUG: Every time I start HS2, it goes through all my devices and throws an error saying they've been changed, and resets the device types to UNKNOWN. Every time.
I'm running two serial ports into VMware from the main machine. One goes to my Ocelot, which I use for X10 PLC communication. The other goes to my MR26A for X10 RF reception. This is my basic need setup. I could use a few more serial ports, but the Equinox board isn't supported by VMware. For testing, this will be ok.
I had to configure the Ocelot and download the MR26A plugin and configure it from the updater. The config went well on the Ocelot, and I had it create all devices for the Ocelot and the Secu-16 I have. The updater worked well, too. However, the config on the MR26A plugin was a little messy. Initially, the config screen opened behind everything on my desktop, and having no tab at the bottom of the screen, I didn't see it. Took a minute for me to find it and configure the thing.
Then, I made a mistake on it, so after saving the changes, I went back into it. After making the change, it said there was no comm port specified, but I hadn't changed that. I saved anyway and restarted HS2, but no MR26A comms. Errors about no comm port.
I went back onto the MR26A config, plugged in the same existing comm port number there, and voila! it worked this time. Saved and restarted, I had MR26A comms now. This is a plugin issue.
BUG: However, I'm getting lots of program errors with it, and eventually it shuts down. Not good, this is my main RF receiver. Oh well... this is a test instance.
I added a few more devices, set up some events and tested. Seems to work ok.
So far, the base program looks pretty good, solid. I don't have the voice working - it doesn't seem to want to allow me to use the new Speaker app locally. I'll look into that later today or tonight. It might be a VMware thing, or it could be the install - I didn't see SAPI5 installed with HS2, so that might be it.
I'm probably not going to install over an older 1.7 install, simply because I'm moving the first of next month, and there's no reason for me to bring an old config forward since so much will be changing soon. I'm sure there will be pitfalls there, too. Read the docs on the HS2 beta release to get the specifics. No doubt you will have to make some manual changes.
Enjoy!
My inital install failed. I guess it installed .NET Framework, but it still errored out. I got the framework separately and installed it, things worked ok this time.
I still don't have TTS though. Not sure why. The Speaker app errors out when I start it. I'll have to look into that.
I initially didn't have the MDAC 2.8 install. HS2 corrupted the newly-created sample.mdb when it "saved" it on shutdown. Result: restarting HS2 hung because the database was corrupt. Nice. Why can't they just check for the right MDAC version BEFORE messing up the db?
I blew away the db and installed MDAC 2.8, then restarted HS2, it rebuilt the blank sample.mdb and off we went!
BUG: I added a few devices. Made a mistake and named two devices the same, HS2 didn't complain, but I couldn't see both devices on the web GUI. They were in the db, however. I renamed the one I could see, the other one came back, but then I had to modify it to make sure the db wasn't messed up. It LOOKS like it would be fairly easy to get the db screwed up by making this mistake again... not sure what the consequences would be. Maybe they need to enforce unique device names, or modify the web GUI so that it shows ALL devices... not sure what the issue is here but I have some ideas.
BUG: Every time I start HS2, it goes through all my devices and throws an error saying they've been changed, and resets the device types to UNKNOWN. Every time.
I'm running two serial ports into VMware from the main machine. One goes to my Ocelot, which I use for X10 PLC communication. The other goes to my MR26A for X10 RF reception. This is my basic need setup. I could use a few more serial ports, but the Equinox board isn't supported by VMware. For testing, this will be ok.
I had to configure the Ocelot and download the MR26A plugin and configure it from the updater. The config went well on the Ocelot, and I had it create all devices for the Ocelot and the Secu-16 I have. The updater worked well, too. However, the config on the MR26A plugin was a little messy. Initially, the config screen opened behind everything on my desktop, and having no tab at the bottom of the screen, I didn't see it. Took a minute for me to find it and configure the thing.
Then, I made a mistake on it, so after saving the changes, I went back into it. After making the change, it said there was no comm port specified, but I hadn't changed that. I saved anyway and restarted HS2, but no MR26A comms. Errors about no comm port.
I went back onto the MR26A config, plugged in the same existing comm port number there, and voila! it worked this time. Saved and restarted, I had MR26A comms now. This is a plugin issue.
BUG: However, I'm getting lots of program errors with it, and eventually it shuts down. Not good, this is my main RF receiver. Oh well... this is a test instance.
I added a few more devices, set up some events and tested. Seems to work ok.
So far, the base program looks pretty good, solid. I don't have the voice working - it doesn't seem to want to allow me to use the new Speaker app locally. I'll look into that later today or tonight. It might be a VMware thing, or it could be the install - I didn't see SAPI5 installed with HS2, so that might be it.
I'm probably not going to install over an older 1.7 install, simply because I'm moving the first of next month, and there's no reason for me to bring an old config forward since so much will be changing soon. I'm sure there will be pitfalls there, too. Read the docs on the HS2 beta release to get the specifics. No doubt you will have to make some manual changes.
Enjoy!