Bug found in BCD396T UASD

[emt331000]

The BCD396T UASD software crashes when trying to write data to the scanner with a Windows Limited User Account.

An error dialogue box opens that says:

Cannot change Visible in OnShow or OnHide.

The box closes after pressing Ok, and is followed by the UASD "Write to Scanner Process" window. But nothing works and UASD must be forcibly shut down with Windows Task Manager.

However, UASD works when I increase the permissions of the Windows account to Administrator.

[DaveNF2G]

I don't think you can classify that as a software bug. It is a security feature of Windows doing its job.

[emt331000]

How do you figure? What job is it doing?

[DaveNF2G]

Keeping a "limited" user account from accessing unauthorized system resources - in this case, the serial port.

[eorange]

That is definitely a bug. No user should ever see the message "Cannot change Visible in OnShow or OnHide.", followed by a lockup.

A better exception handler would describe the problem in plain english and halt the operation.

UPMan may chime in here and suggest a way to submit this bug report to Uniden.

[emt331000]

Originally Posted by DaveNF2G

Keeping a "limited" user account from accessing unauthorized system resources - in this case, the serial port.

I can connect my game controller up to this port, and it works just fine.

Access to any ports (serial, parallel, com) should not be prevented to a LUA unless it was specifically set by an administrator. Even if this is a legit denial, it should never be handled with that error message and application lockup, as eorange said. Properly and securely written applications should run unless they need to modify the system iteself, which UASD should not be doing.

[Jay911]

Which version/flavor of Windows?

[emt331000]

XP Pro SP2

[joelbedard]

The problem rely on the use (to store program information that need to be updated) into the Windows Registry at HKEY_LOCAL_MACHINE (limited account cannot change anything into there) instead of writting them into HKEY_CURRENT_USER (limited user can change information here)

Also, if you install the software beneath "C:\Program Files" folder (using an admin account, but using the software with a limited account), the limited account could not change anything there. Way to by pass that, install the software to another folder, which limited account will be able to read/write content. But what does not change the first issue...

[emt331000]

Originally Posted by joelbedard

The problem rely on the use (to store program information that need to be updated) into the Windows Registry at HKEY_LOCAL_MACHINE (limited account cannot change anything into there) instead of writting them into HKEY_CURRENT_USER (limited user can change information here)

I don't understand what you mean.

Originally Posted by joelbedard

Also, if you install the software beneath "C:\Program Files" folder (using an admin account, but using the software with a limited account), the limited account could not change anything there. Way to by pass that, install the software to another folder, which limited account will be able to read/write content. But what does not change the first issue...

The bug has nothing to do with a local user's permission to write files. Running a program should not depend on administrative privileges unless it is trying to change a system file. UASD isn't trying to do this, I hope! Rather, UASD is trying to change the Visible property of a control. A bug is preventing this from functioning properly.

[dave3825]

The message window is not usad specific

go here and check the links and you might find some info

http://search.yahoo.com/search?p=Can...p=mss&ei=UTF-8