NASLite Network Attached Storage

When NASLite-2 USB gets a version upgrade (say to 2.0.1 or whatever), how do registered users a> get notified of the availability, and b> get the upgrades?

fwiw, I got an email today advising of 2.0's release and how to get an upgrade.

Yes, I received that email that too. But what I'm asking about in this thread is the inevitable upgrades to the 2.00 release (that I've got installed and am currently (and happily) running).

I've got NASLite-2 2.00 (07-2006) running right now. Sometime in the future, I would expect that an updated version, say 2.01, will be released. I am inquiring as to how we, the registered users of 2.00, will be notified of these releases.

All registered users will receive an email notification when new versions are released. You'll download the updated version from the same link you used at purchase.

And when we remake the USB stick, will it still store our configurations or will we have to completely reconfigure the USB stick after each upgrade?

Programming the USB device is like re-installing the OS, so the config will be lost, however here is a process that one can use to avoid the loss of the config data:



Granted, in some cases unlock may be required, but the configuration itself should be preserved. The above approach may not work with all USB Flash drives, but in testing, we haven't had a problem yet.

Hope that helps.

Might wanna make Tonys post a sticky!

I just upgraded 2 NASLite servers from v2.02 to v2.03 using Tony's posted method - all went fine, and no new unlock code was required. However I did note that the FTP service which I had disabled on both servers was re-enabled dispite saving my previous v2.02 settings. If I didn't stumble on it they would have remained enabled and opened. Just FYI.

That is very strange. The config data is saved as a block with an associated checksum. If the saved values are inaccurate then the checksum verification would have triggered an error and the defaults would have been assigned.

I just tried that a few times, varying the settings, but all was as necessary. I think your FTP must have been enabled prior to saving the config. You may want to repeat the process and verify.

If anyone else experiences this, please speak up.

I dropped both servers back to v2.02 and then forward again to v2.03 and I can't repeat my reported "FTP service OFF to ON problem". I guess I must conclude that my FTP service was indeed on instead of off as I believe I had them set. I apologize for the erroneous report.

No problem,

Keeps us on out toes.