problems psr 500

[ShawnCowden]

I cant get my usb cord to work at all with my scanner and I need help with it it might be something about port settings but I did a port scan and it said no scanner found HELP!!!

 

[ShawnCowden]

Windows Vista Btw

 

[tobarger]

Help

The COM port number assigned to the USB cable by your computer. If you are running a Windows operating system, you can find this information under “Ports” in the Device Manager.

 

[ShawnCowden]

yes I know and my port is 41 and psredit will not take that port only up to 32

 

[eyes00only]

I had a hard time too, but I did Win500. The solution was in the software program under configuation, I think.
If I remember correctly, I had to check several port settings before I found one that worked.

JK

 

[mandlair]

And I think you can change the port number in ports in device manager.Mike

 

[mikey60]

yes I know and my port is 41 and psredit will not take that port only up to 32

Edit the PSREdit500.ini file and change the port there. It's in the [Communications] section. I'll add more port values to that drop down for the next release.

Mike

 

[ShawnCowden]

how do i do that mikey

 

[mikey60]

how do i do that mikey

Open the folder where the PSREdit500 program is located. In that folder you should find a PSREdit500.INI file. Double click on it and open it with notepad or any other text editor.

Within that file you'll find a line that looks like this:

[Communications]

That's the start of the Communications section. Just under that line you should see a line similar to this:

Port=32

Change the number in that line to 41 from whatever it is now, and then save the file. As long as you don't go into the serial port editor in PSREdit500, it should work for you.

Mike

 

[mikey60]

how do i do that mikey

I just uploaded an update to PSREdit500 that will allow you to go up to COM64 from the GUI...

Mike

 

[DonS]

I just uploaded an update to PSREdit500 that will allow you to go up to COM64 from the GUI...

Suggestion... why not allow anything that Device Manager will allow (COM1 - COM256)? It's not as if you have to actually populate the control's "data" at edit/compile time - you can just add the strings to the control in your WM_INITDIALOG handler (presuming it's a combo / drop-down list box in a dialog box).

The "slick" way, of course, would be to try to open COM1 through COM256, and only add strings for those ports where CreateFile() doesn't result in ERROR_FILE_NOT_FOUND. (ERROR_ACCESS_DENIED could be used to flag ports that exist but are already opened).

EDIT: Heh... like this if you're using any of my WinXX programs.

 

[mikey60]

Suggestion... why not allow anything that Device Manager will allow (COM1 - COM256)? It's not as if you have to actually populate the control's "data" at edit/compile time - you can just add the strings to the control in your WM_INITDIALOG handler (presuming it's a combo / drop-down list box in a dialog box).

The "slick" way, of course, would be to try to open COM1 through COM256, and only add strings for those ports where CreateFile() doesn't result in ERROR_FILE_NOT_FOUND. (ERROR_ACCESS_DENIED could be used to flag ports that exist but are already opened).

EDIT: Heh... like this if you're using any of my WinXX programs.

It will support it currently if you edit the ini file... Going all the way to 256 would actually not be too hard to do, and I may do that as soon as things settle down a little around here.

MIke