Well, I am rather certain that I had it working on the "BUSINESS" version. (Beta of course)
Then, they sent me a Beta of the ULTIMATE.
That version will not even try to install WINSPM R9.
The way I have my PC set up is I can change operating systems just by removing a HARD DRIVE from a "DRAWER", and sliding another one in it's place, so it's not such a big deal to swap operating systems.
That being said, I am soon to receive a fully licensed version of Vista Business, so I will see if it works or not.
I have the business version and winspm does not work properly. When you right click on the .exe file and set it for windows xp pro capatibility it still won't work. If any one can get this to work I would like to know.
Thanks. I can get it to load and run but when you access the magix it goes into an error (blue screen).
Before I go through the hassle of proving this to myself, I'd like to know a couple of things about your particular installation.
1. Did you upgrade an XP machine that had a working copy of WinSPM on it?
2. Is this a single experience with one machine, or has this been proven on multiple machines?
3. What COM port assignment are you using?
While Vista is a new O/S, we are still talking about emulation software talking to a serial port; nothing complicated. Windows XP has the ability to address a greater number communiation ports (COM10 and up) by using different Base I/O Addresses and Interrupts. That's great, since all the new stuff like printers uses serial ports. But WinSPM won't work in these higher ranges, even on XP.
If this is an upgraded unit, you may have old and unused software/drivers with "hooks" on one of the preferred ports (COM1 or COM2). One sure sign of this is an inability to assign devices (like a modem) to one of these lower port numbers.
describing a technique for freeing up the low-numbered COM ports by killing a "nonpresent device". In this particular post, a previous installation of BlueTooth software had created a "nonpresent device", which unnecessarily occupied the needed serial port.
Answer to #1. no,I did not upgrade. New Dell Vista Laptop with 9.0 winspm loaded on it.
Answer to #2. Just this one laptop (new out of box)
Answer to #3. Could not order laptop with built in serial port. I ordered a USB to Serial adapter. It is using Com Port 4. This adapter works on my other laptop just fine it has XP Pro on it.
Might want to contact Interactive Northwest, the software company that develops Winspm for Avaya. You can bet Avaya won't care since it has been MD'd, unless enough people jump up and down and scream a lot.
OK! Everybody, time to jump up and down and yell and scream at AVAYA before the support window closes.
@ T00-MAT-ATTT (phonetically speaking, except for the zero's)
The system may be MD'd but it is not at end of support yet, is it?
If enough business partners complain because microsoft threw a wrench at the monkey, Avaya might issue a patch.
Heck they issued so many patches for the Definity 3.x, they had to come up with 4.x just so they could get some air before they had to start over again.
MM/Dagwood sorry, I didn't mean to tax your brains with my cryptogram, it is just my old tired brain at 11 pm trying to be silly.
I know this is abit out of date, but instead of worrying
about what doesn't work with WinSPM....get yourself an older
laptop or desktop that will work with XP, Win98, Win95 or
even DOS and stay with what does work...You know Avaya has
never been Tech friendy anyway...so why are you surprised that WinSPM will not be upgraded to work with Vista..and
really who cares???
It would be nice to have one laptop to carry around in stead of two when programming Avaya and other phone systems.
I don't mind changes, if it is for the best. But I don't like it so far.
When you tried to install the WinSPM in Vista did you run the install program in XP compatible mode? Then after that would it install? If it did install, then I would tag every file associated with WinSPM as needing "xp compatible mode".
I had an unrelated piece of software that I couldn't install on Vista until I tagged the install file on the install CD as needing "XP compatible". Then I had to run the program in "compatible mode", but eventually it did install and run.
not sure if it helps, but I thought I'd offer these thoughts.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.