Official Starrsoft WIN500 Software Thread

[Rekd]

Window Size

Win500 works well for me except for the main window being (much) bigger than my desktop (1280 x 768 or 1024 if I recall, I'll look when I get home). I have to scroll the main window to the bottom then scroll the tables to be able to see the bottom of the object tables. It's a serious PITA when trying to move around and do things.

The good news is that remote control works but again is too big for my screen and I have to scroll the tabs out of sight to see the whole thing.

I've got about another week on the trial and downloaded PSREdit last night. It fits better on my screen but I can't use Remote Control because it doesn't support 120dpi Resolution.

Is there a setting (besides column widths and text height) that can fix this very annoying issue? I'm running my resolution as high as it will go on my laptop, and running the software on a different comp is not an option.

I probably won't be buying this software simply for this reason, unless there's a fix that I haven't found yet. (I'll keep playing with the screen settings, but I've done just about everything I can think of on the laptop.)

 

[fmon]

Win500 works well for me except for the main window being (much) bigger than my desktop (1280 x 768 or 1024 if I recall, I'll look when I get home). I have to scroll the main window to the bottom then scroll the tables to be able to see the bottom of the object tables. It's a serious PITA when trying to move around and do things.

The good news is that remote control works but again is too big for my screen and I have to scroll the tabs out of sight to see the whole thing.

I've got about another week on the trial and downloaded PSREdit last night. It fits better on my screen but I can't use Remote Control because it doesn't support 120dpi Resolution.

Is there a setting (besides column widths and text height) that can fix this very annoying issue? I'm running my resolution as high as it will go on my laptop, and running the software on a different comp is not an option.

I probably won't be buying this software simply for this reason, unless there's a fix that I haven't found yet. (I'll keep playing with the screen settings, but I've done just about everything I can think of on the laptop.)

I use 1680 x 1050 at 96dpi and can get all of Web Import dialog side by side with all of main Win500 dialog with these settings.

 

[Rekd]

I use 1680 x 1050 at 96dpi and can get all of Web Import dialog side by side with all of main Win500 dialog with these settings.

Ok. Thanks... Not sure how that's relevant to my problem, but ok.

 

[fmon]

Ok. Thanks... Not sure how that's relevant to my problem, but ok.

That is your problem. 96dpi is normal while 120 is large causing the software to spread further on the display. Changing to more screen resolution will allow the display to cover more area.

 

[Rekd]

I'm at the max already.

I'm running my resolution as high as it will go on my laptop, and running the software on a different comp is not an option.

Mayhaps I should see if there's more current drivers for the video card that will let me go bigger.

 

[fmon]

Originally Posted by Rekd View Post
Win500 works well for me except for the main window being (much) bigger than my desktop (1280 x 768 or 1024 if I recall, I'll look when I get home). I have to scroll the main window to the bottom then scroll the tables to be able to see the bottom of the object tables. It's a serious PITA when trying to move around and do things.

Sorry, I looked at this part of original post and checked my desktop. However, checking my laptop, I have max setting of 1600 x 1200 at 96dpi. This gives me nearly the same final display with Web Import side by side with main Win500 dialog. The two overlap by 1/4 inch. If main dialog is Maximized, the Web Import can even be opened within the unused dark gray area allowing one to observe the import.

 

[DonS]

I'm at the max already.

Mayhaps I should see if there's more current drivers for the video card that will let me go bigger.

The problem is your 120dpi setting.

Win500 will run, without scroll bars on the main window, on a 1024x768 display at 96dpi (Windows' "normal" dpi setting). When you change to 120dpi, you're telling Windows to make everything about 56% larger (25% each horizontally and vertically). Basically, Windows is trying to draw things in "real world" units; if it's trying to draw a 1" square at 96dpi, it will use 96 pixels horizontally and vertically; if you change the dpi setting to 120, Windows will use 120 pixels horizontally and vertically.

At 120dpi, Win500 requires, of course, 1280x960.

Running a 1024x768 display at 120dpi is effectively the same as a same-physical-size 800x600 display at 96dpi.

Reverting to Windows' normal setting of 96dpi will most likely allow Win500 to "fit" on your display.

 

[Rekd]

Thanks, Don, will give it a try when I get home. I'm guessing that has to do with the font settings because that's teh only thing I haven't changed on the laptop to try to solve this.

If that's it, and I can still see my screen without my glasses, I'll be sold on Win500!

 

[Highpockets]

Don, on the Win500 Page, under "What's New" should it be v1.12 not v1.08 for the Remote Client Version, for the win500 v1.73 update.

 

[DonS]

Don, on the Win500 Page, under "What's New" should it be v1.12 not v1.08 for the Remote Client Version, for the win500 v1.73 update.

Yes, it should. I've fixed it... thanks.

 

[DonS]

Experimental version of Win500

I've put an experimental version of Win500 on my web site:
http://www.starrsoft.com/software/win500/win500_ex.zip

This version changes how I communicate with the scanner cable. Instead of using a "COM port" as assigned by Windows, I now talk to the cable directly. It's my hope that, once this code has been tested sufficiently and makes it into the "released" version of Win500, the change will eliminate the COM port assignment / selection confusion.

EDIT: I'd be interested in hearing whether or not various Windows configurations already have the required FTDI drivers installed.

If you want to try this version, download the ZIP file from the link above and replace your existing Win500.EXE with the version from that ZIP. You may need to update your FTDI drivers. The program will prompt you if that's necessary, but you can also get the required drivers directly from FTDI via this link to the FTDI site. That should get you an executable that will install the latest "certified" version.

This version of Win500 doesn't care about any "COM port" settings. You should be able to either a) select a different COM port within Win500's "configuration" dialog or b) change the COM port assignment via Windows Device Manager. Either "change" (which would normally keep Win500 from seeing the cable) should have no effect. EDIT2: You should also be able to "disable" the COM port in Device Manager, under "Ports (COM & LPT)" - the COM port will no longer exist, but this version of Win500 should still be able to talk to the cable/scanner.

CAVEAT: This version does not support multiple "USB Scanner Programming Cables" connected at once. If you're using such a configuration, you may want to keep using the "released" version of Win500. I'll soon be adding code to distinguish and choose between multiple instances of the cable.

 

[kevins669]

Don, this is very cool. Works great!

I already use the latest drivers, so I had no problem there. You may want to update the dialog box when it can't connect to the cable. The device was actually in use, but the dialog box just tells me to go get the new drivers. May cause some confusion, so you may want to put both as possibilities.

When you get multiple device support, that would be even better! I use Remote Desktop to get into my "radio" machine from remote to view activity and do miscellaneous things with Win500, outside of 500Client. This makes operation much easier.

Perhaps you can do the same with the audio devices - Win500 does not like to show me the different sound card inputs, when opening Win500 through Remote Desktop. It just shows lots of symbols.

No big deal, but it comes in handy when streaming multiple instances.

Thanks again!

-- Kevin

 

[DonS]

Don, this is very cool. Works great!

I already use the latest drivers, so I had no problem there. You may want to update the dialog box when it can't connect to the cable. The device was actually in use, but the dialog box just tells me to go get the new drivers. May cause some confusion, so you may want to put both as possibilities.

I've added some more informational text to the message(s) that pop up, warning about not having the cable plugged in, having it already 'in use' by another app, etc.

When you get multiple device support, that would be even better! I use Remote Desktop to get into my "radio" machine from remote to view activity and do miscellaneous things with Win500, outside of 500Client. This makes operation much easier.

If you're using Remote Desktop like I sometimes do: "pushing" the COM ports through the connection so that Win500 running on your local machine can "see" the COM ports on the server machine and connect to the scanner physically connected to the server... that likely won't ever work with this new method of communicating with the cable. The FTDI drivers, used as I'm using them in this experimental version, only let you talk to cables that are physically connected to the local machine.

Perhaps you can do the same with the audio devices - Win500 does not like to show me the different sound card inputs, when opening Win500 through Remote Desktop. It just shows lots of symbols.

Another Remote Desktop -ism. The audio devices are re-mapped to the local machine and Win500 running on the server can no longer "see" the audio inputs on that server machine. I run into this all the time: I am often connected to my primary PC via Remote Desktop. Win500 is running on that primary PC. If, for some reason, I need to stop/restart the Win500 server, I have to go upstairs to the office and do it there - I can't restart the Monitor/Control process remotely, since the audio device is no longer present (I get a "WAVEIN" error from Windows).

 

[DonS]

I put up a new version of the experimental Win500:
http://www.starrsoft.com/software/win500/win500_ex.zip

It shows some better messages if it cannot open a connection to the cable, and also has a couple of bug fixes. The version number didn't change (it's still 1.73), but the time stamp of the EXE should now be 10:46 PST.

 

[kevins669]

Thanks, Don. The new method does indeed work with Remote Desktop - since I am not at home right now, I went ahead and did it all from remote - and absolutely flawless. Are you logging into the console or just a new connection? I go to the open console, and this method does work with the new experimental edition.

I figured there was really nothing that could be done with the AudioIn...But, I do find that I can start/stop the monitor and still get audio, just as long as I don't have to exit the program. That will obviously always cause the error, since I started Win500 in the RD session.

Anyway, thanks again, Don.

-- Kevin

 

[kevins669]

I put up a new version of the experimental Win500:
http://www.starrsoft.com/software/win500/win500_ex.zip

It shows some better messages if it cannot open a connection to the cable, and also has a couple of bug fixes. The version number didn't change (it's still 1.73), but the time stamp of the EXE should now be 10:46 PST.

Just tried this version, but the error message is the same...The version is the 10:46 one...

Users can be a pain, sometimes

-- Kevin

 

[DonS]

Thanks, Don. The new method does indeed work with Remote Desktop - since I am not at home right now, I went ahead and did it all from remote - and absolutely flawless. Are you logging into the console or just a new connection? I go to the open console, and this method does work with the new experimental edition.

The new cable connection method works RD if Win500 is running on the _server_ machine.

I was referring to running Win500 on the RD _client_, connecting to a cable that's plugged into the _server_.

For example, this works for me:
* PC #1 directly connected to PSR-600 via USB/Serial cable on COM8
* Win500 runs on PC #1 connecting to COM8
* PC #2 connecting to PC #1 via Remote Desktop

This also works for me:
* PC #1 directly connected to PSR-600 via USB/Serial cable on COM8
* PC #2 connecting to PC #1 via Remote Desktop
* Remote Desktop "maps" PC #1's "COM8" to PC #2's "COM5"
* Win500 runs on PC #2 connecting to COM5

The first configuration (Win500 running on machine that's physically connected to scanner) will work with the new Win500.

The second configuration, though, should not work with the new Win500 - since PC #2 (the RD "client") won't be able to see the cable connected to PC #1 (the RD "server").

I do have an "audio problem" in the first configuration: If I have RD configured to "bring the server's sound to the local machine", I get an error when I try to start Monitor/Control. However, if I leave sound at the server, it works just fine. My way around this (when I need to stop/restart the Win500 server app) is to disconnect from RD, re-configure the audio, reconnect to RD, restart the Win500 server, then disconnect/re-configure/restart the RD connection.

 

[DonS]

Just tried this version, but the error message is the same...The version is the 10:46 one...

Oops. Looks like I didn't actually do a 'Release' build after I changed the text.

A new version is up (EXE time stamp 11:26 PST). I've verified that running two copies, starting monitor/control on one then trying to start it on the other, does result in my new text.

 

[kevins669]

The new cable connection method works RD if Win500 is running on the _server_ machine.

I was referring to running Win500 on the RD _client_, connecting to a cable that's plugged into the _server_.

For example, this works for me:
* PC #1 directly connected to PSR-600 via USB/Serial cable on COM8
* Win500 runs on PC #1 connecting to COM8
* PC #2 connecting to PC #1 via Remote Desktop

This also works for me:
* PC #1 directly connected to PSR-600 via USB/Serial cable on COM8
* PC #2 connecting to PC #1 via Remote Desktop
* Remote Desktop "maps" PC #1's "COM8" to PC #2's "COM5"
* Win500 runs on PC #2 connecting to COM5

The first configuration (Win500 running on machine that's physically connected to scanner) will work with the new Win500.

The second configuration, though, should not work with the new Win500 - since PC #2 (the RD "client") won't be able to see the cable connected to PC #1 (the RD "server").

I do have an "audio problem" in the first configuration: If I have RD configured to "bring the server's sound to the local machine", I get an error when I try to start Monitor/Control. However, if I leave sound at the server, it works just fine. My way around this (when I need to stop/restart the Win500 server app) is to disconnect from RD, re-configure the audio, reconnect to RD, restart the Win500 server, then disconnect/re-configure/restart the RD connection.

Wow, I did not even think about running it in the second example. I am definitely going to try that with the release version of Win500. Very cool.

I have tried numerous ways of getting around the audio, too. When I test #1 with the release version, I am going to take a look at your method for audio, too.

Thanks for the great new ideas!

-- Kevin

 

[DonS]

I have tried numerous ways of getting around the audio, too. When I test #1 with the release version, I am going to take a look at your method for audio, too.

It also works with the "experimental" version. I'm running that version on my "primary PC", and just re-started it via RD from my laptop.

I only thought of that method this morning. It was really a hassle having to run upstairs every time I wanted to restart the Win500 Monitor/Control stuff (and was much more of a hassle if I wasn't home and was using RD/VPN). Previously, I had gone so far as to add boot-time scheduled tasks that would start things up (Win500 and TCPMux), and I would actually re-boot the machine remotely if I needed to re-start Win500. The problem with that workaround is that I don't actually see Win500 (or the two instances of TCPMux) unless I bring up Task Manager, since they were running before anyone logged on.

Thanks for making me think about it a little more... this is much easier.