> -----Original Message----- > From: email@example.com [mailto:owner-cbm- > firstname.lastname@example.org] On Behalf Of Scott > Sent: Monday, June 13, 2011 5:57 AM > To: email@example.com > Subject: RE: ZoomFloppy > > > > > -----Original Message----- > > From: firstname.lastname@example.org [mailto:owner-cbm- > > email@example.com] On Behalf Of Nate Lawson > > Sent: Monday, June 13, 2011 1:23 AM > > To: firstname.lastname@example.org > > Subject: Re: ZoomFloppy > > > > On Jun 12, 2011, at 3:51 AM, Scott wrote: > > >> > > >> There is a ZoomFloppy mailing list at google groups for these > kinds > > of > > >> questions. You may get a more prompt reply there in the future. > > >> > > >> The ZF doesn't use a drive letter. It's not a mass storage device. > > It > > >> sounds like you have some kind of third-party software installed > for > > >> your flash drive ("LaunchU3"). It is possible this driver doesn't > > >> understand the ZF (a USB device with two bulk pipes but it is > > vendor- > > >> specific, NOT mass storage) but it is still trying to claim it. > > >> > > >> I'd try uninstalling the LaunchU3 program and see if that helps. > You > > >> don't need a special driver for USB flash drives. They've been > > >> supported natively in Windows since Win2k. > > >> > > >> -Nate > > >> Message was sent through the cbm-hackers mailing list > > > > > > Nate, > > > > > > Def odd. LaunchU3.exe is the files that gives you the U3 Task bar. > > The Flash > > > drive normally takes two drive letters, one being a CD-ROM drive. > But > > no > > > matter what drive letters I give it, it seems the ZF has already > > taken them. > > > Like the ZF takes ALL the available drive letters when connected. > > > > > > I'll see if anyone on the ZF google group has had this problem. > > > > > > Thanks to the quick response. > > > > > > The ZoomFloppy does not use any drive letters (none). I think the > > driver for the U3 hardware is behaving improperly. If you uninstall > the > > U3 driver and let the Windows native driver handle the USB flash > > portion, you shouldn't see any problems. > > > > -Nate > > Message was sent through the cbm-hackers mailing list > > Nate, > > Interesting... > > I looked in the 'Uninstall or change a program' and LauncherU3 WAS > installed. I uninstalled it and then ran CCleaner Registry cleaner and > then > rebooted. Plugged in the ZF and then the U3 Device. I got the same > error. I > looked again in the 'Uninstall or change a program' and LauncherU3 was > not > there. The autorun.inf file is listed below. > > [AutoRun] > open=LaunchU3.exe -a > icon=LaunchU3.exe,0 > action=Run U3 Launchpad > > [Definitions] > Launchpad=LaunchPad.exe > Vtype=2 > > [CopyFiles] > FileNumber=1 > File1=LaunchPad.zip > > [Update] > URL=http://u3.sandisk.com/download/lp_installer.asp?custom=188.8.131.52&bran > d=Pel > icanBFG > > > [Comment] > brand=PelicanBFG > > The two Drive letters used by the U3 Device are below > > Drive Letter Drive Type Drive Name Drive Description > Connected Instance ID Device Path Last Update Time > G:\ Local Hardware SanDisk SanDisk Cruzer USB Device > @cdrom.inf,%gencdrom_devdesc%;CD-ROM Drive Yes > USBSTOR\CdRom&Ven_SanDisk&Prod_SanDisk_Cruzer&Rev_8.02\1100400A5A92CC3C > &1 > \Device\CdRom2 6/13/2011 5:39:33 AM > H:\ Local Hardware SanDisk SanDisk Cruzer USB Device > @disk.inf,%disk_devdesc%;Disk drive Yes > USBSTOR\Disk&Ven_SanDisk&Prod_SanDisk_Cruzer&Rev_8.02\1100400A5A92CC3C& > 0 > \Device\HarddiskVolume4 6/13/2011 5:39:43 AM > I know that my Western Digital USB Drive doesn't run software to > install a > CdRom so I don't get the error. So it seems to be tied to the CdRom. > The > CdRom seems to be a requirement in order to get the U3 Application Menu > because when I double click LauncherU3 after the error I get the error > again. > > > Message was sent through the cbm-hackers mailing list Also, With the U3 device installed and getting the error, if I unplug the ZF and double click LauncherU3 it launches normally without error. Message was sent through the cbm-hackers mailing listReceived on 2011-06-13 11:00:03
Archive generated by hypermail 2.2.0.