+clegg78 Posted October 2, 2005 Share Posted October 2, 2005 (edited) Ok so heres teh back story: A few years ago I bought Topo USA for my GPS III+, and on a trip I busted one of the CD's in half... happened to be the install CD. So I didnt think much of it since I had it installed already. I got a new PC last week and I wanted to get Topo reloaded on the box. I had a backup I made of the CD (like I do all my CD's because I am a super clutz and scratch them... ) but I backed them up with some crappy software that truncated some names. Since I dont have the serial # any longer (beacuse when I stepped on the case I shattered it) Garmin wont talk to me. What I need are the full file names for the TDB directory and the Unitcode directory on the West CD. for the e:\TDB folder all I have is this for names: 04/08/1999 02:34 AM 333,824 TOPO10~1.IMG 11/09/1999 04:40 AM 96,725 TOPO10~1.TDB 04/08/1999 02:34 AM 333,824 TOPO10~2.IMG 11/09/1999 08:40 AM 1,749 TOPO10~2.TDB 04/12/1999 05:19 AM 1,597,440 TOPO10~3.IMG 11/11/1999 10:33 AM 182,797 TOPO10~3.TDB 04/12/1999 06:04 AM 911,360 TOPO10~4.IMG 11/11/1999 11:04 AM 180,997 TOPO10~4.TDB I need to know what those names are supposed to be. For the e:\unitcode folder all I have is: 07/15/1999 05:19 AM 507,904 006702~1.BIN 08/26/1999 10:39 AM 655,360 007802~1.BIN 10/25/1999 09:15 AM 618,008 011102~1.RGN 10/13/1999 02:48 AM 507,904 011802~1.BIN 08/30/1999 10:52 AM 589,824 011902~1.BIN 09/08/1999 09:14 AM 589,824 012902~1.BIN 10/26/1999 02:10 AM 598,016 UPDATER.EXE Since the file sizes should be the same for anyone else who owns this, I would appreciate some help fixing this. Sucks that if I cant fix this that I am out a $100+ peice of software... Please help! Edited October 2, 2005 by clegg78 Quote Link to comment
+TresOkies Posted October 2, 2005 Share Posted October 2, 2005 tdb 04/08/1999 08:34 AM 333,824 Topo100Alaska.img 11/09/1999 10:40 AM 96,725 topo100alaska.tdb 04/08/1999 08:34 AM 333,824 Topo100Hawaii.img 11/09/1999 02:40 PM 1,749 topo100hawaii.tdb 04/12/1999 11:19 AM 1,597,440 Topo100USE.img 11/11/1999 04:33 PM 182,797 Topo100USE.tdb 04/12/1999 12:04 PM 911,360 Topo100USW.img 11/11/1999 05:04 PM 180,997 Topo100USW.tdb UnitCode 07/15/1999 11:19 AM 507,904 006702000204.bin 08/26/1999 04:39 PM 655,360 007802000210.bin 10/25/1999 03:15 PM 618,008 011102000204.rgn 10/13/1999 08:48 AM 507,904 011802000206.bin 08/30/1999 04:52 PM 589,824 011902000203.bin 09/08/1999 03:14 PM 589,824 012902000202.bin Email me if you need more details. Quote Link to comment
+tls11823 Posted October 2, 2005 Share Posted October 2, 2005 So you took your original disks - not the backups - on a trip and destroyed one of them. Then you obliterated the serial number. Then you called the vendor with questions about a disk that you claimed was a copy of your valid disk and they didn't want to talk to you. And this is Garmin's fault? Quote Link to comment
+clegg78 Posted October 3, 2005 Author Share Posted October 3, 2005 I didnt say it was garmins fault. I work in software development so I know what they have to do. I just was pointing out so when someone told me "call garmin" that I had tried and got the expected reply. And yes, I took the original discs on a trip, stepped on the case, busted one CD, and the others seemed to survive. so I threw the busted up case out (not realizing I never wrote down the serial#, and used a copy I made to my HD of the CD's to run the ap since then, which seemd to work until I tried installing from there. But its all good now, I am back happy Quote Link to comment
+FlyfishermanMike Posted October 3, 2005 Share Posted October 3, 2005 That's weird. What program did you use to back up your disks? It shouldn't have renamed those files like that. Anyway, I wish they'd update their Topo software. Or at least make the 24 scale availible everywhere. ^^ike Quote Link to comment
ardfarkle Posted October 4, 2005 Share Posted October 4, 2005 (edited) The naming error was probably caused by selecting standard ISO 9660 verses adding the Joliet extensions needed for long file names. This limited the burning software to using 8.3 filenames as shown in your example. Edited October 4, 2005 by ardfarkle Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.