Also my webcam stopped after a while and I could never find why.
It is something within the Windows 2000 (advanced) server.
I tried them both with the same result.
Eventually I switched to Windows 2000 and now it works fine.
This is not a great an answer but I know that WD is not working correct with the 2000 server.
So, my guess is that this is a good technical challenge for the Writers of this software.
Years ago, I had a similar problem with VWS and they had a special patch to correct the problem and I have been using it till now, but sincerely I would love to use WD instead.
I really like the look of the interface
So, any help into resolving this issue would be appreciated.
Maybe you could try the running the debug version (on the weather-display download page) and see what errors it logs? Otherwise you could ship the developer a multiprocessor server with 2k pro server installed and he could work on it
i am not sure exactly what is wrong or needed to be changed
maybe its a security settings?
or any compatibility command lines could be added when starting up the program?
I don’t think Brian develops with the Win2k (Advanced) Pro Server so that might not happen. Kinda hard to track down that type of issue without a test platform to test it on.
It might be something specific to Win2K Pro. I don’t know if anyone else is running the same platform with success. If there are, perhaps they can offer some suggestions.
the win95/nt version (which i can update), does not have the labjack USB built in…which is what causes wd to spit the dummy…at start up…if no USB support in windows
Hmmm. If you have it running on Win2K Pro, it should be possible to get it running on the server. I run several advanced 2K servers at work…at least until we can get rid of them.
Was a MS partner until they ran all us little shops out a couple years back. The code for 2K server/Pro is a common base.
You see nothing in your Server Event viewer when WD crashes?
According to what I see on the 'net, that does have USB support e.g. “Windows 2000 Advanced Server supports the latest advances in networking and peripheral hardware, including USB devices”, but maybe it’s not enabled?
Wdisplay begin it’s loading process and after 2 to 3 seconds disappear from the process list.
I do not think that Wdisplay has to have a weather station intalled to load the initial splash screen.
For the records I prefer to use a serial port.
also for the ecords I operate a HOBO H21 with all the trimmings and a OREGON SCIENTIFIC WS-918 which the ws-918 is the station I would like to run with Wdisplay instead of VWS…
USB is also enabled on this machine and works fine with Fingerprint ID and a USB camera for Facial Recognition.
I also use 1-wire ligntning detector and solar detector
[quote author=yanhend link=topic=20818.msg162681#msg162681 date=1166400284]
USB is also enabled on this machine and works fine with Fingerprint ID and a USB camera for Facial Recognition.
/quote]
Is this machine “locked down”? When I read your post intially “security” came to mind. Enable failure auditing through the local security policy and see if WD is trying to access something it can’t.
I just successfully installed and loaded WD on my Windows 2000 Advanced Server at work. This is a 4 CPU Xeon box that has all the latest MS patches and tons of security lockdowns in place. Took me 2 attempts to get it installed:
Attempt 1:
Accepted default path of c:\program files\wdisplay
got attached errors when the install attmepted to register DLL’s and complete install.
Attempt 2:
Problem looked path related so I added c:\wdisplay to my server PATH and then ran install again. This time I changed default install path to match my newly added system path c:\wdisplay. Install ran perfectly and I was then able to launch WD and start configruing it no problem. This is a work machine so I obviously don’t have a toy attached (nor can I).
Seems to me this proves that WD CAN be installed on a Windows 2000 AS MP machine!
