Welcome, Guest. Please login or register.

Author Topic: TD64 or NSD for new storage drivers?  (Read 8318 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline freqmax

  • Hero Member
  • *****
  • Join Date: Mar 2006
  • Posts: 2179
    • Show all replies
Re: TD64 or NSD for new storage drivers?
« on: February 20, 2013, 02:19:42 AM »
Now I know why I like free open source stuff ;)

Points to consider:
 * Reliability - clearly defined API etc (trashed filesystem is bad)
 * Compatibility
 * Performance (CPU and kB/s)

Probably the documentation CD etc.. was created in a propietary setting. And when the financial trouble started there was the likely hood that a corporate buyout deal might happen etc. When things run out in the sand, everything got stuck in a big mess. Because I suspect that when Commodore  was working you would had the info with a bit of cash (+NDA?) without any problems.

This is why systems with documentation in your physical possession is such a good idea.
« Last Edit: February 20, 2013, 02:24:39 AM by freqmax »
 

Offline freqmax

  • Hero Member
  • *****
  • Join Date: Mar 2006
  • Posts: 2179
    • Show all replies
Re: TD64 or NSD for new storage drivers?
« Reply #1 on: February 21, 2013, 08:30:59 AM »
Found all the filesystem limits!

http://thomas-rapp.homepage.t-online.de/filesyslimits.html

I think this page perhaps gives more insight?
http://thomas-rapp.homepage.t-online.de/4gb_faq.html
« Last Edit: February 21, 2013, 08:45:08 AM by freqmax »
 

Offline freqmax

  • Hero Member
  • *****
  • Join Date: Mar 2006
  • Posts: 2179
    • Show all replies
Re: TD64 or NSD for new storage drivers?
« Reply #2 on: February 22, 2013, 09:02:16 AM »
Do there exist any filesystem driver example in C ?
 

Offline freqmax

  • Hero Member
  • *****
  • Join Date: Mar 2006
  • Posts: 2179
    • Show all replies
Re: TD64 or NSD for new storage drivers?
« Reply #3 on: February 22, 2013, 12:57:03 PM »
My idea were to provide a filesystem API in one end. And send all requests to a server in the other end.