Roy wrote:
> On Jun 29, 5:23 am, Paul <nos...@needed.com> wrote:
>> Roy wrote:
>>> On Jun 28, 9:41 pm, Paul <nos...@needed.com> wrote:
>>>> Roy wrote:
>>>>> Hello Paul
>>>>> I was able to downloaded the file and immediately run it but
>>>>> regardless if the USBflash drive plugged is suspected to be defective
>>>>> or intact , it does not react...Is there a special way to run this
>>>>> software?
>>>>> Thanks
>>>>> Roy
>>>> If there is no reaction, then the USB flash is dead. It could be that
>>>> there is a break in where the connector meets the PCB, inside the flash
>>>> packaging.
>>>> You should also test, with a known to be working USB device. That
>>>> will demonstrate how the program is supposed to work, and also prove
>>>> there isn't a problem with the USB ports on the computer you are
>>>> using for this testing.
>>>> I also use a couple Linux LiveCD distributions, for hardware testing.
>>>> Knoppix (knopper.net) and Ubuntu (ubuntu.com), can be booted from
>>>> their respective CDs, without installing any software on the hard
>>>> drive. Using programs like dmesg, lspci, and lsusb in Linux, you
>>>> can list/enumerate the hardware that the OS can "see". But UVCView
>>>> should be doing the same thing, with a much smaller investment
>>>> in time and effort. Those Linux distributions, are a 700MB download.
>>>> Any time I need to prove "it's a hardware problem", I boot one of
>>>> the Linux CDs, and see if the symptoms look the same. For example,
>>>> my first computer had a video (AGP) problem, and the symptoms
>>>> existed in both Windows and Linux.
>>>> Paul
>>> I did try using a working USB device such as the flash drive,
>>> wireless mouse dongle, it does not react... or does it need more time
>>> for its operation? Whenever I click the close icon it states that "
>>> windows cannot close the program, it may need more time for its
>>> operation etc".
>>> Further
>>> the caption says:
>>> 16 Bit MS-DOS Subsystem
>>> D:\UVCVIE~1.EXE
>>> C:\DOCUME~\ROYBAS~1\LOCALS~1Temp\. A temporary file needed for
>>> initialization could not be created or could not be written to. Make
>>> sure that the directory path exists, and disk space is available.
>>> Click close to terminate the application
>>> This surprises me is as I never experienced this with previous command
>>> prompt application.
>>> I don't understand why would it have an issue of disk space when I
>>> still have 35 gigs of free space in my hard drive
>>> BTW Sorry
>>> I am not familiar with linux applicationeither..
>>> Roy
>> UVCView.x86.exe should execute immediately when you double click it in
>> a folder window. File size is 167,231 bytes. It is not a DOS program.
>>
>> When it starts, it should look very similar to this.
>>
>> http://www.die.de/blog/content/binary/usbview.png
>>
>> I don't know right off hand, what versions of Windows it supports.
>> I'm using it on Win2K right now, and it is fine. Something else
>> is going on with your system, would be my guess. Are you seeing
>> any other strange problems, or is this the only one ?
>>
>> Paul- Hide quoted text -
>>
>> - Show quoted text -
>
> I have never experienced such peculiarities with other programs and
> only with that UVCvie...
> My PC is run by WinXP Sp2.
> I could never get it to display the appearance that you showed here
> http://www.die.de/blog/content/binary/usbview.png
>
I've been looking for another copy, and there is one here.
ftp://ftp.efo.ru/pub/ftdichip/Utilities/
File size is 167,232 bytes.
MD5sum is 93244d84d79314898e62d21cecc4ca5e
The MD5sum matches the download from the Microsoft site, so seems
to be legitimate. Give that one a try and see if the behavior is
any different.
Maybe someone else understands the significance of -
"16 Bit MS-DOS Subsystem"
because I don't. Presumably it is an important clue. I'd
almost suspect malware, or alternately, an important file
on your C: drive is corrupted. I tried looking on the
Microsoft site, and so far, don't see an exact match
for the symptoms.
Paul