> I would suggest you create one (or maybe two) library files and > control the functionality with constants before the include. > Within the library file, you could optionally include other files, eg > the file that does non-defragmented files (to replace the 'simple' > read.
I will try using constatns as you suggested. I hope it will still fit on 16F877 > How do you get files on you disk with your first library? If you can > answer that, I think it is usefull to release it. > It would be very usefull if you could read, write and delete a file - > even if write means you have to specify it's max size in advance or > so. Currently you have to add files to your fat32 formatted hard drive via your pc. Here is an easy way to do so: 1. Disconnect the drive (IDE & Power Cable) from your circuit. 2. Put your hard disk into an external drive enclosure 3. Plug the external enclosure's usb cable into your pc. 4. Windows will pick up your enclosure right away so you can add, remove and edit files. 5. Drive must be defragmented with windows before putting it back onto your circuit. HOWEVER... I can easily create a "write to existing file" function that would go in the first releaes. Adding a new filename and alocating space for the file via fat32 lib not be available for a while as it is quite complicated. The additional functions that can be created such as create file, delete file, copy file, move file, etc. could be easily ammended to the lib in future releases. Would this be sufficient? On Aug 19, 3:59 am, Joep Suijs <[email protected]> wrote: > Fat32 with only 50 bytes of RAM. Impressive! > > I would suggest you create one (or maybe two) library files and > control the functionality with constants before the include. > Within the library file, you could optionally include other files, eg > the file that does non-defragmented files (to replace the 'simple' > read. > > There are a few advantages for this aproach: > - There is only one include for the user to remember. > - You don't duplicate code (or only to a very limited level). > > How do you get files on you disk with your first library? If you can > answer that, I think it is usefull to release it. > It would be very usefull if you could read, write and delete a file - > even if write means you have to specify it's max size in advance or > so. > > 2009/8/19 mattschinkel <[email protected]>: > > > > > > > Some of you may know that I am working on fat32 libs. > > This current version will fit on 16F877 with 50 ram to spare and also > > works on 18F452. > > > I have a working version that is able to do the following: > > -list files a directory > > -go to a directory > > -go to a file > > -read a file (file must be defragmented) > > > In the future, there are lots more functions that can be added, such > > as: > > -create a file > > -write to a file > > -create a directory > > -read a file that is not defragmented > > > Should there be different lib versions with different pic memory > > requirements? > > > The difference between reading a defragmented file and a fragmented > > file is great. fragmented files will take more memory space and > > processing time. > > > Should I release a 16F877 version with 50 bytes ram left on the chip? > > Many people do have 16F877 in there tool box, they may want to try it > > out before they upgrade there pic. > > > If I do make different versions, how should I name the libs? eg. > > fat32_v1.jal, fat32_v2.jal, etc.- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
