If you just want to transfer files and do not need SMB to work, aka being able to use "network drive" etc, you can simply use FTP and then it's super easy to setup. You can use something like filezilla for a server and whatever client works on 98 (total commander?).

To avoid connecting to the internet when plugged into the router - configure network settings manually (IP/netmask) and do not set default gateway.

Thanks. I forgot to add that the older PC has a Belkin PCI card, the old dial up modem has long since been removed.

Stovebolt_66 wrote on 2025-07-09, 16:17:

Thanks. I forgot to add that the older PC has a Belkin PCI card, the old dial up modem has long since been removed.

You can FTP over any internet connection... not just a dial-up.

Couple other things worth mentioning:

The older system probably supports an older/insecure version of SMB. I've not done this in W10, but at least W7 could
be configured to support older SMB versions (which are disabled by default).

If you really want to block the older machine from the internet, you can probably do so in your router, allowing it
to connect to other things on the local network, but not the internet gateway.

I move files over the network between DOS and Win7/Win10 all the time. This also works well in
W98 and requires DosBox on the Win64 end... If this might be of interest, I can post details.

I move files over the network between DOS and Win7/Win10 all the time. This also works well in
W98 and requires DosBox on the Win64 end... If this might be of interest, I can post details.

If you don't mind I would be interested, I already have DosBox and DosBoxstaging on the new machine, I use them to run some of the early DOS based racing sims.

I'll add that I don't necessarily have to block the internet from the old PC, it's just that I'm leery of trying to connect it with Win98. In trying to educate myself and reading thru this forum and others, I gather there are lots of folks still accessing the net with Win98 no problem, but they are much more computer savvy than I am and I think some are using some sort of home-built browser, which is again way, way over my head. The old PC sat in my closet for years; I kept it even after I upgraded to newer PCs with newer OS. It's a really good machine and I really like W98se. I'm not working full time anymore and decided to fire the old one back up, it was like seeing a long-lost friend when the home screen came up.

Stovebolt_66 wrote on 2025-07-09, 16:17:

Thanks. I forgot to add that the older PC has a Belkin PCI card, the old dial up modem has long since been removed.

Dial up modem would be useless for what your trying to do so that is fine.
Double checking the Belkin card is a standard network card and not wireless?

Simplest option would be connect both computers to your router via ethernet cables.
Then as Archer57 said use a ftp program to transfer the files as this doesn't care what versions of windows you are using.

Technically the Win98 PC would have internet but it will be safe behind the router firewall and for the few hours of gaming would pose almost no risk.
(this is similar to my setup and never had an issue)

Windows networking uses SMB as DaveDDS mentions. This can be made to work but takes alot more effort. Personally I prefer this as I find it more convenient with over 10 machines.
but ftp not only gives you faster transfer speed but alot less initial setup required

chinny22 wrote on 2025-07-10, 05:48:

Windows networking uses SMB as DaveDDS mentions. This can be made to work but takes alot more effort. Personally I prefer this as I find it more convenient with over 10 machines.

My issue with that is - it requires enabling a bunch of insecure legacy stuff on modern system to work. It is not the end of the world, but a disadvantage to consider. Especially if modern system is a laptop and may get connected to public wifi or something at some point.

It is possible to build a linux NAS which would run 2 different instances of samba on different interfaces sharing the same storage, one configured to be compatible with old stuff, another - with new stuff. I've been meaning to do that for a while, even did software configuration required, but... i am lazy and i just transfer stuff using thumb drives. The biggest thing that is stopping me from doing this is having to add extra switch and cables to each old system - that'll add significantly to already quite bad rat's nest of cables...

There is also something special about having truly offline system this days, with no network connected at all...

DaveDDS wrote on 2025-07-09, 18:33:

Couple other things worth mentioning:

The older system probably supports an older/insecure version of SMB. I've not done this in W10, but at least W7 could
be configured to support older SMB versions (which are disabled by default).

W10 support SMBv1, you need to enable it in control panel>programs and functions>turn windows features on or off>SMB 1.0/CIFS file sharing service.

But in my opinion, I had so much issues trying to get my SMBv1 share from server 2k3 r2 working on w10 that I just gave up on it. IIRC XP will work with the more secure SMBv2 shares used on server 2012 r2.

Stovebolt_66 wrote on 2025-07-09, 19:18:

If you don't mind I would be interested, I already have DosBox and DosBoxstaging on the new machine, I use them to run some of the early DOS based racing sims.

I have a thread about it, see: DDLINK: Easily move files between/To/From DOS systems

Be aware that it doesn't provide "shares", it is literally a file transfer
program. It's really nice in DOS because unlike FTP you don't need a TCP
"stack" or any other networking protocol support installed.

All you need is a DOS "packet driver" for you network card (these are
readily available for many NICs).

And since it uses a proprietary network protocol that is not-routable, it is
very secure against the "outside world".

DDLINK can also transfers files over PARALLEL (pretty much only DOS<>DOS
and SERIAL (also works with DosBox).

It is a 16-bit DOS program, it will run under 32-bit windows but not 64-bit
so you have to use DosBox. Under Win32 you can use something like SWSVPKT
to provide a packet driver - you'll need a network enabled DosBox (and
something like WINPCAP to enable DosBox virtual NE2000 NIC) om Win64.

Thanks everybody! I'll try out some of this and see where it goes. I feel kind of dumb, a jump drive to transfer files never occurred to me, I'm so old fashioned and behind the times I was trying to avoid burning cd's to that. I still would rather have the two connected, and learning how all this stuff works is really interesting and I'm enjoying that part of it. You folks are great!

Stovebolt_66 wrote on 2025-07-10, 12:38:

Thanks everybody! I'll try out some of this and see where it goes. I feel kind of dumb, a jump drive to transfer files never occurred to me, I'm so old fashioned and behind the times I was trying to avoid burning cd's to that. I still would rather have the two connected, and learning how all this stuff works is really interesting and I'm enjoying that part of it. You folks are great!

Don't feel dumb. USB was still in early days during Win98 so is slow and can be a challenge to find a drive that likes Win98.
Network on the other hand was already well established so still more reliable in the long run

DaveDDS wrote on 2025-07-09, 18:33:

... I move files over the network between DOS and Win7/Win10 all the time. This also works well in
W98 and requires DosBox on the Win64 end... If this might be of interest, I can post details.

I probably should have also mentioned that if you have any trouble getting a network "packet"
interface to work in Winblows98 - you can always boot it to DOS, load a standard DOS packet
driver and still do transfers.