Trouble with 64HDD
in [Commodore]
|
From: Andrew Wiskow on 12 Nov 2006 07:11 I've got to be missing something, and I'm hoping someone here can help me. I've set up 64HDD on an older PC, and I've been over the documentation several times... But I can't for the life of me figure out how to save files with long filenames on the drives I create under 64HDD. I have the -lfn flag set in the go64hdd.bat file, and when it starts up it says that Long Filenames are enabled, and when the program is running on the PC, at the top of the screen, off to the right, are the letters "LFN", so it should be working, right? But when I write a simple Basic program on the C64 and try to save it, anything longer than 8 charachters gets chopped off. I noticed, too, that from the PC side, if I go to the directory where I saved the file, it will be listed using the DIR command (cut to 8 charachters with a .PRG suffix), but if I use the LDIR command, the file doesn't show up at all! Can someone help me? I have a feeling that I'm missing something simple here... I just can't figure out what it is. I've tried running 64HDD from two different PC's, and with both I get the same result. -Andrew
From: James @ cbm264 on 12 Nov 2006 10:28 Andrew, Which OS are these older PCs running? A short bit from Nick's website: "64HDD supports D64, D71, D81, T64, LNX images and also the Native MSDOS file system. The MSDOS mode supports Commodore 16-character filenames in Win95 LongFileName format if the LFNFILES plug-in has been downloaded and configured (zip includes "Odi's LFN tools"). " The LFN plug-in is here: http://www.64hdd.com/64hdd.html, near the bottom of the page, under "Download Optional 64HDD Plugins". James www.cbm264.com Andrew Wiskow wrote: > I've set up 64HDD on an older PC, and I've been over the documentation > several times... But I can't for the life of me figure out how to save > files with long filenames on the drives I create under 64HDD. > > Can someone help me? I have a feeling that I'm missing something > simple here... I just can't figure out what it is. I've tried running > 64HDD from two different PC's, and with both I get the same result.
From: Andrew Wiskow on 12 Nov 2006 15:51 James @ cbm264 wrote: > Andrew, > > Which OS are these older PCs running? Like I said, I tried it with two... One was a dual-boot system I set up with MS-DOS on one partition and Windows XP on another. Of course, I ran 64HDD out of DOS. The other PC has MS-DOS and Windows for Workgroups 3.11. Again, I ran 64HDD out of DOS. > A short bit from Nick's website: > "64HDD supports D64, D71, D81, T64, LNX images and also the Native > MSDOS file system. The MSDOS mode supports Commodore 16-character > filenames in Win95 LongFileName format if the LFNFILES plug-in has been > downloaded and configured (zip includes "Odi's LFN tools"). " > > The LFN plug-in is here: http://www.64hdd.com/64hdd.html, near the > bottom of the page, under "Download Optional 64HDD Plugins". I know that already... I have the plugin, and as far as I can tell, I have it set up properly. When 64HDD starts up, it says that Long Filename support is available. But again, when I save a file from the C64, the filenames are getting cropped. Any ideas? -Andrew
From: Andrew Wiskow on 12 Nov 2006 16:48 Here's something else I've just noticed... With LFN enabled in 64HDD, my files are getting cropped to 8 charachters, and if I send a command to scratch a file, nothing happens. I get: 01,FILES SCRATCHED,00,00 But... if I run 64HDD *without* LFN enabled, I get 8 charachter filenames, as I would expect, but if I send a command to scratch a file, the file gets scratched as it should. I get: 01,FILES SCRATCHED,01,00 This is driving me crazy... What am I doing wrong? Why isn't 64HDD working as it should with LFN enabled? -Andrew
From: user on 12 Nov 2006 23:49
"Andrew Wiskow" <drewbrasil(a)yahoo.com.br> wrote in message news:1163368123.029943.51730(a)m7g2000cwm.googlegroups.com... > Here's something else I've just noticed... With LFN enabled in 64HDD, > my files are getting cropped to 8 charachters, and if I send a command > to scratch a file, nothing happens. I get: > 01,FILES SCRATCHED,00,00 > > But... if I run 64HDD *without* LFN enabled, I get 8 charachter > filenames, as I would expect, but if I send a command to scratch a > file, the file gets scratched as it should. I get: > 01,FILES SCRATCHED,01,00 > > This is driving me crazy... What am I doing wrong? Why isn't 64HDD > working as it should with LFN enabled? > > -Andrew > Just a guess.. Try loading doslfn prior to accessing your 64HDD. http://www.geocities.com/jadoxa/doslfn/ |