BCD396T UASD "Unable to insert a line" error

[35delivery]

I'm running BCD396T UASD on a Windows 98SE machine. Documentation says that this version of Windows is supported. All the system requirements (RAM, disk space, etc.) listed as UASD requirements have been met. The scanner is connected via the serial cable that was supplied with the scanner. All of the preloaded systems are on the scanner. The serial connection is good. I can use the UASD to control the "Online Control" with no problem. However, when I try to use the "Connect to Scanner" it gives me the initial screens and begins downloading all the preloaded systems. About two thirds of the way through this exercise (Quick Key 52, somewhere in Texas), the download fails with the error "Unable to insert a line". I believe this is a Windows 98 error which indicates that a ListBox line maximum of 32736 rows has been exceeded. Has anyone else seen this error? Is there a fix or work around? Any help appreciated!

[cpuerror]

Windows 98 has some memory limitations that aren't present in 2k or later. Once UASD starts demanding a lot of memory it probably just flops out and gives you that message. My .02 would be to upgrade.

[35delivery]

cpuerror, thank you for your input! I'm trying to use this computer because it has a serial port and my other machine only has USB which I would have to convert via converter cable and drivers. The WIN98 machine also has other software which I use that is not supported on later versions of Windows, so an upgrade would be a major undertaking. I tried manually increasing the swap space, but this had no effect. I think I could delete some of the preprogrammed systems from the scanner and reduce the size of the list in WIN98; but doing this would effectively limit my usage of the scanners memory capacity to about 50% of what is available, if I want to use this software. I was hoping to find some upgrade to WIN98 which would increase this ListBox limit.

[cpuerror]

I would just pony up the 10-15bucks on ebay and get a usb adaptor and use it on the newer machine. Just not subjecting myself to Win98 is well worth the money.

[35delivery]

That's probably what I'll do if I can't turn up any fix for Win98. Also I really don't need all those preloaded systems on the scanner so I might just delete the ones I'm not using.

[UPMan]

It is a Windows 98 memory issue. There is no fix short of updating the operating system.

If you are trying to back up the preloaded stuff...all that comes with UASD already, so there should be no need.

[35delivery]

Originally Posted by UPMan

It is a Windows 98 memory issue. There is no fix short of updating the operating system.

If you are trying to back up the preloaded stuff...all that comes with UASD already, so there should be no need.

UPMan, thanks for your input. I'm not trying to do a backup, it actually fails after you click the "Connect to Scanner" button. UASD then tries to load an image of what is on the scanner into the display, before it shows "connected". I suspected all along that it was a Windows 98 issue. I think the best solution for me may be to just delete preloaded systems that I'm not using from the scanner. If I should need to use one of these systems, I'm assuming they could be re-input into the scanner from the preloaded data base supplied with UASD. Correct?

[UPMan]

Well, the only reason to "Connect to Scanner" is to make a backup (or make a really long printout of what is in the scanner). You don't have to do that if you want to write systems to the scanner.

[35delivery]

Originally Posted by UPMan

Well, the only reason to "Connect to Scanner" is to make a backup (or make a really long printout of what is in the scanner). You don't have to do that if you want to write systems to the scanner.

True, BUT.......I think you must "connect" before you can "write", UNLESS you allow the software to erase scanner memory. After editing the system(s) using the data base screen, you then press the "Write to Scanner" button. You enter the "write to scanner process" and select the "write options". If you uncheck the "Erase memory before writing" box the "Write" button at the bottom of the screen changes to "connect". If you then press the "connect" button at the bottom of the screen, the software displays "Connecting....." and "Reading system information" until it encounters the ListBox limit and then the software exits with the "Unable to insert a line" error. No write takes place. I did not want to erase scanner memory because I have some systems in the scanner which I input "manually" using the control knob and the scanner menu functions. Since the software exits before the existing image can be read, all the "manually" input systems would be lost. Is there another way to write (new systems to the scanner) where existing scanner memory remains unchanged without using the connect process (which fails)?

There are only three ways I can think of to get around this problem:

1. Get off Windows 98SE and onto a later version. (Which for me has some problems, see my earlier posts.) I have not heard of any Windows 98SE fixes for this problem.

2. Use the control knob and scanner menu functions to manually delete enough preloaded, unused systems to get the scanner memory below the ListBox limit. I estimate this would be about 50% of the scanner memory. My scanner memory usage currently shows 67%.

3.Get Uniden to revise the UASD software in a future release to do multiple, smaller scanner reads in the connect code so as not to exceed the ListBox limit. Not sure how feasible this is, but currently UASD documentation indicates that Windows 98SE is supported.

[UPMan]

Ah, yes. I nearly always Erase, so had forgotten about that.

4. Create a new configuration with only those systems you need, then "Write to Scanner" with the "Erase" option selected. I am assuming your desired setup is less than 50% of scanner capacity.

I have on my to-do list to revise the documentation to add the Windows 98 caveat, but this comes up so rarely it slips off the radar fairly quickly.

[35delivery]

Originally Posted by UPMan

Ah, yes. I nearly always Erase, so had forgotten about that.

4. Create a new configuration with only those systems you need, then "Write to Scanner" with the "Erase" option selected. I am assuming your desired setup is less than 50% of scanner capacity.

I have on my to-do list to revise the documentation to add the Windows 98 caveat, but this comes up so rarely it slips off the radar fairly quickly.

I think the correct procedure would be:

A. Perform my procedure (2),
2. Use the control knob and scanner menu functions to manually delete enough preloaded, unused systems to get the scanner memory below the ListBox limit.

B. Use the connect to scanner UASD function to load the image of the reduced scanner memory which will include all the manually entered systems and some preloaded systems.

C. Save the manually entered systems into UASD data base.

D. Perform your procedure (4),
4. Create a new configuration with only those systems you need, then "Write to Scanner" with the "Erase" option selected.