• Please review our updated Terms and Rules here

What is the best way to move files from my modern desktop to my 486?

G

Gribnitz

Experienced Member
Joined
Nov 4, 2013
Messages
161
Location
St Louis
On my Amiga 4000 I use a null modem, or move a CF card back and forth. On my C64 I use a SD Card and a QuadPortIEc. What can I do use for the old PC's and compatibles? There has to be a fast and easy way.
 
Installing a CD-ROM drive and just burning CD-ROMs. Alternatively a more modern machine that connects to old machines over an IPX network (or Brutman's TCP/IP FTP solution). Basically the same thing.

I use diskettes most of the time. Not fast but pretty convenient. You can also use a LapLink cable with an older desktop or notebook (Pentium 4 or equivalent).
 
I use floppies for small files, or if I need to move a larger file I boot into Win3.11 and use windows filesharing (my 486 has an ethernet card)
 
Depends on the hardware and configuration at both ends.

- If you've got serial and/or parallel ports at both ends, null modem cable and transfer/network software.
- Parallel/serial to ethernet adapter and FTP
- ZIP drive or swappable hard disk.
- Bluetooth wireless using RS-232<>BT adapter.
 
Seems like you have to answer this same question every week or two for somebody. Don't the people who keep asking this question have a computer? :)
 
I use CF cards and notebook SATA drives. You can get drive bays for easy access.
 
I also use Compact Flash on my 486 system, a lot easier for me to work with as I have a USB reader for my laptop and a built in reader in my desktop. CF cards are also easy to find in small sizes, such as 128 MB as a lot of the "cheap" cameras of the early 2000s used CF and came with the small sized cards.
 
Mau1wurf1977 said:
I use CF cards and notebook SATA drives. You can get drive bays for easy access.
Click to expand...
Assuming that your "old PC" has an IDE port and CF adapter and you prefer sneakernet (albeit with larger sneakers) to being connected, preferably wirelessly...

But yes, for loading more or less static images like the all-games-on-one cards and carts for C64s,VIC20s etc. cards are nice.
 
Caluser2000 said:
I'd go with Chucks' suggestion http://www.uncreativelabs.org/index.php?site=howtos|msdosnet.php
Click to expand...
Definitely one of the more convenient once it's set up; it does use more memory on the client than some of the other approaches and can be a little tricky to install (especially on a modern server), and of course you need a compatible NIC, a place to plug it into, drivers, (and probably a 'null-modem' cable ;-) )

As usual, there's no 'best way'; like I said, it depends on what's available, the configuration at both ends, etc.:
- What's the OS (MS/Linux/Mac/?)?
- What version?
- What ports/interfaces are available?
- What cards/cables/parts in the junk box?
- How much $$ is it worth?
- Is it a one-time transfer or an ongoing thing?
- Is disk/card swapping OK?
- Is double-ended control acceptable (terminal s/w) or does it have to be controlled from the client?
etc. etc.

No shortage of discussion here and 'out there'...
 
Last edited:
I agree, hard to know what suits, I often change strategy depending on what's around me.

For a 486 that is permanently setup, I'd personally just use Windows 3.11 for Workgroups with TCP/IP added on. But if it's a collection of machines, I'd grab a 'give-away' Pentium laptop and fill it's HDD with goodies, drag it around with a null modem hanging off. (My only trouble with this, is I have 20 of them, and I can't remember what I put on which laptop).

Also love the Syquest drives, I need to get more.
 
You could also go to a "state of the art" solution and hook up a Vinculum configured for USB flash to a convenient RS-232 port on the olde machine.

The amount of memory taken up by LANMAN doesn't bother me--I use MSDOS 6.22 (although 5 would also work) and have a menu selection in my CONFIG.SYS that asks if network drivers should be installed. The default is "no".
 
The plain old floppy disk works fine in many cases. Otherwise its WfW 3.11 with its built in networking.
 
Most of my systems are 8088-based and trying to get NETBEUI working on them is something I revisit every 5 years, always with pain and suffering. So I just use mTCP and FTP files around, which has worked fantastically as long as mTCP has exited (4+ years IIRC).
 
I've set up NetBEUI on 2 8088 machines and an AT&T 6300. Just followed directions (on the web) and never had any problems. I found that setting up networking on Warp 3 connect was far more troublesome.
 
You must log in or register to reply here.
Back
Top