I don't actually have an internal ftp server (yet) but I would just point it to the same location as my current drivers folder.
Mine are sorted by brand so
Asus
Compaq
Creative
etc...

Then part number, followed by the device
Asus\P2B-DS\NIC
Asus\P2B-DS\SCSI
Asus\P4P800\Chipset
Asus\P4P800\Sound

I used to then group by OS but that got a bit messy as often say DOS and 9x were included in the same driver package
Worst case I'll create a index.txt if the folder looks a bit "full"

Not saying that's the best way, I definitely have duplicates, say chipset for my few BX motherboards, but gets around issues when sometimes 1 bit of hardware doesn't like the latest driver.

Also have no wish to make it publicly available, I used to but will just upload to vogons drivers now and not worry about bandwidth/security/etc

I suppose the question that's bugging me the most is that, for the purpose of sharing on a LAN, zipping up and using filenames without spaces is not necessary and is low-maintenance, whereas managing FTP is potentially high-maintenence (at least initially).

I guess it's a moot point anyway - I'm going to have to use best practice for the FTP files so there's no point making work for myself by having uncompressed versions too.

I have been actually working on something like this for sometime now, a few years ago i had a failed hdd with some rare stuff gone and ive been slowly building up a collection on my NAS along with a backup drive (learned my lesson, back-up, back-up, back-up).
Anyways Ive been wanting to create a simple ftp server for all of this. if any one wants to help me with building this archive that would be great.
so far my archive is basically like this:
Drivers/A.M.D/Windows 7, 8, 10/Video Adapter/Catalyst Software Suite 15.7.1 (64 Bit).exe
Catalyst Software Suite 15.7.1 (64 Bit).txt
Radeon Software Crimson Edition 15.12 (64 Bit).exe
Radeon Software Crimson Edition 15.12 (64 Bit).txt
Windows 98, ME/Video Adapter/Catalyst Software Suite 4.132655.exe
Catalyst Software Suite 4.132655.txt
Catalyst Software Suite 4.137192.exe
Catalyst Software Suite 4.137192.txt
Catalyst Software Suite 6.2.exe
Catalyst Software Suite 6.2.txt
Windows 2000/Video Adapter/ (to many to list)
Windows Vista, 7/Video Adapter/ (to many to list)
Windows XP/Video Adapter/ (to many to list)

just to give u an idea of how i organize, the other folders are filled as well and i have other drivers from 3dfx down to via drivers.
The txt file are to point to witch video cards work with that driver example:Catalyst Software Suite 6.2.txt
Radeon® 9800 series
Radeon® 9700 series
Radeon® 9600 series
Radeon® 9500 series
Radeon® 9200 series
Radeon® 9100 series
Radeon® 9000 series
Radeon® 8500 series
Radeon® 7500 series
Radeon® 7200 series
Radeon® 7000 series
Radeon® Xpress 200 series
Radeon® X850 series
Radeon® X800 series
Radeon® X600 series
Radeon® X550 series
Radeon® X300 series

Would there be interest in a low-fi version of VogonsDrivers.com that's more accessible to non-CSS or text-only browsers?

I just now realised I've never tested it in Arachne or Lynx or similar.

that would be cool would that also be view-able in internet explorer 5.01, 5.5sp2 and 6sp1 as well

I did something like this: ftp://retronn.de/driver/
Also with mirroring a few other sites here ftp://retronn.de/mirrors/
Notable also the mdscene.net (used eg. by the Driver Database of the Win98 Super CD): ftp://retronn.de/mirrors/ftp.mdscene.net/
I have to admit, I don't have the time to sort all this stuff into vogonsdrivers.

elianda wrote:

I have to admit, I don't have the time to sort all this stuff into vogonsdrivers.

The aim of VogonsDrivers was originally just to be a place to put files that had no other home. E.g. all the stuff from Malik's thread that was tied up in Megaupload/Rapidshare/etc.

It was never meant to make other people's archives pointless/obsolete! 😀

Don't get me wrong, I think it's cool that it's grown to the size that it had, but I never want people to feel like the *must* use it.

So, how's this tickle everyone's fancy?

http://www.vogonsdrivers.com/lofi/

It's W3C HTML 2.0 verified, so should render correctly on everything down to NCSA Mosaic.

Oh, and since the move to a VPS, the site has its own IP address, so doesn't require the HTTP Host field to work correctly. Hello IE 1.0!!

Awesome. I like the way you actually bothered to render a page, rather than just enable directory listings!

Another site I am on uses an old Mac as a Hotline server for stuff like that.