From: sharx35 on 6 Jan 2007 22:43 "R. C. White" <rc(a)grandecom.net> wrote in message news:12q0qvqsp7pmq3b(a)corp.supernews.com... > Hi, Steve. > > One or two more thoughts... > >> Cables look ok. > > Can you simply unplug the cables, then plug them right back in again? > > It might sound like a useless exercise, but it has often solved problems > for me. My first computer, the original TRS-80 that I got in December > 1977, used several "edge connectors", much like the PCI connectors on > today's motherboards. Often, corrosion would build up on the metal > "teeth" of those connectors. We often had to give them the "Pink Pearl" > treatment: We would unplug the connector and "erase" those teeth using a > rubber eraser that accountants always needed; "Pink Pearl" was a popular > brand name for those. After erasing, we would plug them in and our erratic > errors would disappear for a while. Often, we didn't even need to erase; > just the friction of unplugging and plugging 'em back in cleaned off > enough corrosion to do the trick. > > This trick still works with modern computers sometimes. Not as often as > in the old days, but sometimes. We called it "reseating the boards" in old PDP's. > >> Haven't run any other HD >> tests - is there some freeware around for this, or do I need to >> purchase a program somewhere? > > There probably are some free generic test programs. I already mentioned > the two I used (PowerMax and SeaTools), which are provided free by the HD > makers. They are targeted at those companies' products, of course, but > they should work on just about any drive. Do you know who made your > drive? Have you tried Dell's tech support? > > RC > -- > R. C. White, CPA > San Marcos, TX > (Retired. No longer licensed to practice public accounting.) > rc(a)grandecom.net > Microsoft Windows MVP > (Currently running Vista Ultimate x64) > > "Steve" <teu(a)qprc.inv> wrote in message > news:r3isp2t5itni6p5lnqpcim7bgoej91j903(a)4ax.com... >> "R. C. White" <rc(a)grandecom.net> wrote: >>>Well, I don't see much in your hardware that should be giving any >>>trouble. >>>Are you using a network of any kind? >> >> Nope, just my one little ol' desktop. :) >> >>>What happens if you unplug the USB HD before trying the backup? What >>>does >>>Disk Management say about that drive? Have you used DM to assign a >>>semi-permanent letter to that drive, or does DM assign it whatever is >>>available each time you plug it in? >> >> It has a permanent drive letter. No change when it's unplugged. >> >>>Have you rechecked all your cables and other physical connections, or run >>>any HD tests? >> >> Chkdsk found no errors. Cables look ok. Haven't run any other HD >> tests - is there some freeware around for this, or do I need to >> purchase a program somewhere? >> >> Thanks again for all your time and effort on this! Obviously, it's >> not confidence-inspiring to get these error messages - I've been >> holding off on entering any new data until we can maybe figure out >> what's wrong... >
From: Steve on 11 Jan 2007 09:37 >Oops, sorry for leaving out the details. Using Q2004 Premier under >WinXP Home. Backing up to another partition on the hard drive, plenty >of space, it's the same partition I've always used with no problems. >Tried backing up to a diferent partition just for the heck of it, no >change. >The error messages seem to change each time - >Unable to open source file > File not backed up >or >Unable to close file > Unable to load item list file > Unable to >reload current file after copy > File backed up successfully >Either way, the file seems to back up ok. And the file itself seems >intact. Validation finds no errors. I'm now using a recent backup file that works with no problems. It's located in \Quicken\Backups. But when I move the file to \Quicken, I get the error messages again. -- The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true. ....James Cabell
From: R. C. White on 11 Jan 2007 16:57 Hi, Steve. HOW are you moving the file to Quicken? Assuming that the good file is C:\Program Files\Quicken\BACKUP\Steve2.QDF, then the proper command would be: C:\>Copy "C:\Program Files\Quicken\BACKUP\Steve2.*" "C:\Program Files\Quicken\Steve.*" You must enclose the entire pathname in quotes because of the space in the "Program Files".folder name. And you must move ALL the related files in the Steve2.* fileset, not just Steve2.QDF. And, you want to eliminate the "2" from "Steve2", so that you don't end up with a backup set named "Steve21" when Quicken adds a "2" to "Steve2". The Copy command will overwrite the existing bad(?) Steve.* fileset in \Quicken, so you may want to rename that first (or move it out of the Quicken folder), just for historical reference in case you want to try to analyze it later to find out what went wrong. When you are sure you don't need it anymore, delete it. When manipulating Quicken data files, it is almost always best to let Quicken do it, rather than use the Windows Copy, Move, etc., tools. When Quicken handles the job, it automatically updates its internal pointers so that it knows where to look for what it needs next time. If we use Windows tools, then WE have to figure out how to update those pointers. You'll find most of Quicken's file-handling tools under its File menu. To let Quicken handle this, click File | Restore Backup File. Browse to the good file you've found and let Quicken load it. When it is loaded and running, click File | File Operations | Rename. Browse to it in the Quicken folder and rename it to Steve.qdf, or whatever name you prefer. RC -- R. C. White, CPA San Marcos, TX (Retired. No longer licensed to practice public accounting.) rc(a)grandecom.net Microsoft Windows MVP (Currently running Vista Ultimate x64) "Steve" <teu(a)qprc.inv> wrote in message news:voicq2tpgg8jr25erqdl4lo9ic15agl649(a)4ax.com... > >Oops, sorry for leaving out the details. Using Q2004 Premier under >>WinXP Home. Backing up to another partition on the hard drive, plenty >>of space, it's the same partition I've always used with no problems. >>Tried backing up to a diferent partition just for the heck of it, no >>change. >>The error messages seem to change each time - >>Unable to open source file > File not backed up >>or >>Unable to close file > Unable to load item list file > Unable to >>reload current file after copy > File backed up successfully >>Either way, the file seems to back up ok. And the file itself seems >>intact. Validation finds no errors. > > I'm now using a recent backup file that works with no problems. It's > located in \Quicken\Backups. But when I move the file to \Quicken, I > get the error messages again.
From: Steve on 12 Jan 2007 14:15
"R. C. White" <rc(a)grandecom.net> wrote: >To let Quicken handle this, click File | Restore Backup File. Browse to the >good file you've found and let Quicken load it. When it is loaded and >running, click File | File Operations | Rename. Browse to it in the Quicken >folder and rename it to Steve.qdf, or whatever name you prefer. Thanks again! I used Q to restore the file from \q\backup to \q. When I open the \q\backup file, it backs up with no problems. But when I open the restored \q file, I get the error messages again (although the file actually seems to back up ok, as before). This is driving me nuts. Sigh. -- That a belief is useful does not mean it is true. ....Unknown |