(I know it's the same thing, but it's easier to me to only have to look in Sound for relevant sound/music tools than scroll through a list of hundreds of programs, even if sorted / ordered.)

For me too, in fact I used that very same software listing that your link provides to build my own repo on my mainWin 7 PC in hopes to transfer them all to the FD PC via a USB Flash Drive.Now though, it looks like I'll have to resort to using optical drives instead.

So, obviously, kernel and shell are supremely important, but the changes were minor (2040 -> 2042) or even non-existent (FreeCOM).

Sorry, but I don't know what you mean by(2040 -> 2042) …

I wouldn't recommend to overload yourself with worries about updating literally everything. I dislike having a billion files that are all falsely considered "important".

I agree with that, trouble is, I'm not sure what's important or what may become important eventually.So, for me, it's easier & quicker to just do it all (I guess you could call that the "hoarder" approach):)

I would suggest focusing only on your most commonly used utils and system drivers (e.g. JEMM).

That's basically what I did.'Fraid I don't even know what "JEMM" is.

Honestly, a lot of stuff hasn't seen major changes.

That's what I've come to the conclusion of too, just wasn't sure if that was the case given the amount of time that's occurred between my initial 1.1 install and now.

And for things like compilers (e.g. FPC), the upgrade path is usually to delete and reinstall from scratch anyways.

Compilers?In an OS?Way beyond me!:)I thought compilers were only used in programming languages, like Pascal, C++, assembly etc.… (???)

Yes, always have backups, if possible, but I don't think you need to backup literally everything.

Well, I wanted to err on the side of caution (given my luck)so I tried to do the FD install backup, but for some unknown reason, the backup failed, the machine seemed to lock-up.Upon rebooting, I re-started the install W/O the backup option & had success that way.

I guess you could always cat or dd from atop *nix the relevant partition into a .img file.

cat or dd ??Is that the same as "DIR"? (Sorry, you lost me here.)

Or, for Windows, use something like this:

Thanx, I ended up using a different util though to produce a boot-able CD from a FDOS 1.2 *.iso file.

take up a ton of space but are also quickly updated / obsoleted, so it's not worth preserving them to backup, IMHO, without a good reason.)

Again, for me, difficult to determine what is & what's not important.Space, for me, on that PC is not relevant.

Is this an ancient machine?

Not ancient, but old! It's a Pentium III/733mhz, Floppy drive, CD/DVD optical drive, 30gb HD, 4gb RAM, AGP video card (not sure what speed & how much vid RAM), & the USB ports (all 2 of 'em) aren't compatible, evidently, with my other networked PCs (I think, but not sure, it's a USB 1.1 vs. a USB 2.0 issue. Or it could be FAT 16 vs FAT 32, again, not sure.For now though, while I determine the issue, I'll be using the optical drives for any DATA transfers..

Why can't he backup to USB jump drive instead?

Isn't USB 1.1 & 2.0 supposed to be compatible?My 2.0 flash drive wasn't recognized on my FD 1.1 USB PC.Is there a util that can list available drives like in in Win & in Linux?

A good boot floppy can be useful, I'm not disagreeing.But overall it's a very limited medium for backups.

Agreed, but that's what I ended-up using. (a boot-able Floppy with my version of *.bat & *.sys files.)

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Freedos-user mailing list

Reply via email to