Pete: I have no idea why this is happening. Its very strange that BPT doesn't start when connecting, but it goes away when disconnecting. >>> ptorpey@xxxxxxxxxxxxxxxx 01/20/06 09:36AM >>> Rob, Regarding the two suggestions you had below: 1. When I checked the properties of the e: drive which showed up about 30 seconds after the BP was connected, I saw: a. Type of disk = removable media 2. Type of File system = FAT Windows did not indicate whether this was FAT16 or FAT32. Is there another way to check? This is a 2 GB card. 2. Checking in the Task Manager as you suggested, I saw that bpl.exe was listed as a running program as it should be. Still when I connect the BP here is everything that happens: 1. I hear the two beeps indicating that the BP is connected. 2. After about 30 seconds, the e: drive pops up listing the files on the BP. 3. Bookport Transfer does not automatically pop up. 4. If Bookport Transfer is started manually, all files show up properly within Bookport Transfer. 5. After disconnecting the BP, the proper tones are played indicating that the BP has been disconnected, and both the e: drive and Bookport Transfer program shut down as they should. Well, any more thoughts? Thanks. -- Pete E-mail: ptorpey@xxxxxxxxxxxxxxxx -----Original Message----- Date: Thu, 19 Jan 2006 10:00:12 -0500 From: "ROB MEREDITH" <rmeredith@xxxxxxx> Subject: [bookport] Re: Bookport Not connecting Pete: There are two things in play here. First of all, I think the long delay your are experiencing is because you are using a FAT32 card with the new beta. FAT32 is just slower when connecting, and it doesn't appear that anything can be done about it. If you aren't using FAT32, let me know. Secondly, if Book Port Transfer works properly when started by hand, but it doesn't start automatically, this is a problem related to our launcher, bpl.exe. Make sure bpl.exe is running. To do this, Hit Ctrl+Shift+Escape to open the Task Manager, move to the Processes tab, and look for bpl.exe. It must be running for things to work properly. Rob Meredith >>> ptorpey@xxxxxxxxxxxxxxxx 01/18/06 11:04AM >>> Rob, Unfortunately I no longer have access to the old computer. I did, however, reinstall the beta software. Now, after I connect the BP: 1. I immediately hear the Windows tone indicating that a connection has been made with the USB port. 2. After about 30 seconds, a window comes up on the PC showing the E: drive as the Bookport and also showing the files on the Bookport. 3. The Bookport Transfer program itself does not automatically pop up as it always has before using this new computer and new BP software. 4. If I manually start the Bookport Transfer program it works properly and shows all books on the Bookport. My system is a Windows XP Home system, I have administrator rights, and it's a 2.6 GHz processor. Although this seems to be workable now, something isn't quite right if the Bookport Transfer program isn't automatically launching and it takes so long to recognize the Bookport as the E: drive. Thanks for any suggestions. -- Pete -----Original Message----- Date: Tue, 17 Jan 2006 09:29:17 -0500 From: "ROB MEREDITH" <rmeredith@xxxxxxx> Subject: [bookport] Re: Bookport Not connecting Pete: Try the Book Port on your old computer to be sure it still recgonizes the Book Port after the firmware upgrade. Let me know. Rob Meredith >>> ptorpey@xxxxxxxxxxxxxxxx 01/14/06 08:20PM >>> I had been testing/using the Bookport's beta software and firmware. Now, I have a new computer, and the Bookport software I have loaded on this new computer does not recognize that I am testing/running betas. Therefore, the automatic beta upgrade was not available. So, I uninstalled the Bookport software and installed the Bookport software from the AFB beta site. All went well with the install. Now the problem... 1. When I connect my Bookport via the USB cable, Windows says that it cannot find the "E:" drive and the Bookport is not recognized. 2. If I launch the Bookport program and then try to connect the Bookport, the unit is still not recognized. Note, I have a D: drive (DVD), but no E: drive on my computer. I know there is a solution for this but forgot what to do. Can anyone help? Thanks. -- Pete E-mail: ptorpey@xxxxxxxxxxxxxxxx