Long File Name device driver

Anything QL Software or Programming Related.
Post Reply
Martin_Head
Aurora
Posts: 869
Joined: Tue Dec 17, 2013 1:17 pm

Long File Name device driver

Post by Martin_Head »

I have been playing around with a directory device driver that supports long file names (up to 72 characters). By adding a path to the start of any file name provided by the operating system. On a per job basis.

So each job could have a LFN1_ device pointing at a different directory on the same storage medium.

This is just a proof of concept, So don't expect everything to work...

This is a screen shot showing DIR with and without the added path
Image1.png
Image1.png (6.68 KiB) Viewed 3109 times
I even got QPAC2 to recognize it
Image3.png
Image3.png (4.19 KiB) Viewed 3109 times
It is based on the FDI2 device driver, and a manual can be found here http://www.dilwyn.me.uk/utils/FDI2Manuals204.zip
Attachments
LFNdriver.zip
(111.84 KiB) Downloaded 258 times
LFNnotes.pdf
(30.95 KiB) Downloaded 283 times


Derek_Stewart
Font of All Knowledge
Posts: 4065
Joined: Mon Dec 20, 2010 11:40 am
Location: Sunny Runcorn, Cheshire, UK

Re: Long File Name device driver

Post by Derek_Stewart »

Hi Martin,

Your new Long File Name device driver looks really good.

I used to use QVFS, but it was quite hard to use.

I will try your device on the Q68, which runs SMSQ/E v3.34, so should work the same way.


Regards,

Derek
RWAP
RWAP Master
Posts: 2850
Joined: Sun Nov 28, 2010 4:51 pm
Location: Stone, United Kingdom
Contact:

Re: Long File Name device driver

Post by RWAP »

Excellent - there was the sub device driver also, but from memory it failed on WDIR or WCOPY....

Rich


Martin_Head
Aurora
Posts: 869
Joined: Tue Dec 17, 2013 1:17 pm

Re: Long File Name device driver

Post by Martin_Head »

RWAP wrote:Excellent - there was the sub device driver also, but from memory it failed on WDIR or WCOPY....

Rich
Not sure if I tried WDIR or WCOPY. If you use WSTAT, it gets a little upset if it encounters a long file name that has been chopped down to 36 characters with the '....' in the middle.
The file size is displayed as 'not found', but carries on regardless. I don't quite know why WSTAT tries to open each file to get the file size and update date, when these can be obtained from the directory which it had to access anyway. Unless it's some sort of hang over from Microdrives.


Post Reply