Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
I have here a desktop computer running Windows XP and a laptop computer running Windows for WorkGroups 3.11. What I want to do is transfer a large file from the desktop to the laptop using a regular phone line. I read somewhere that this can be done using the Terminal application. If so, how? And if not, how else?

To find others similar do a 3.x search above^. I don't know if it will work with xp though. My suggestion is like everyone else's. Try a null modem cable for parallel ports and laplink for faster than modem sharing. or remove the laptop hd and put in another computer transfer the file and replace.
http://computing.net/windows31/wwwboard/forum/10182.html

Okay, I've searched and found a ton of topics on the subject. So far I've gathered that, supposedly, FastLynx 3.2 and higher is capable of transferring information between an XP system and a 3.11 system. If this is true, how would I go about it, assuming I was willing to purchase a parallel cable? Also, wouldn't a parallel cable cause conflicts because the computer uses that port for the printer? (LPT1)

When you use a program such as FastLynx or LapLink just unplug the printer cable and replace it with the Parallel Cable for the transfer session. You will get no conflict and your printer will still work when it is plugged back in. You can buy a LPT2 Port Card if you want to provide a permanent second connection.
A 'Null Modem' Cable is for Serial Transfers (Also called a Yellow LapLink Cable). Use a Data Transfer Cable (which is also called a Blue LapLink Cable) for Parallel use.

Also look at PARCP if you want to use Parallel Laplink Cable, can be run from a Boot Disk on both PC's
http://joy.sophics.cz/parcp/index.htm
If you run from a boot disk it would not know the port is used for the printer!!!
FastLynx is more expensive and has no LFN support:
http://www.sewelld.com/FastLynx3.asp
no LFN support in LapLink V either:
http://www.laplink.com/products/llv/overview.asp
but no LFN support in FileMaven either but it is FREE and runs from Boot Disks:
http://www.briggsoft.com/fmdos.htm
btw I hope XP is not on NTFS as DOS can not read/write NTFS without expensive software. Maybe two NIC' and a crossover cable would do the job................

If you want to go the Xover ethernet cable and two NIC route look at:
http://www.wown.com/j_helmig/wfw311.htm

Thanks for that info. I'm assuming that any parallel DTC will work for my purposes. Windows XP is indeed on NTFS, but FastLynx claims to have a "DOS slave" that allows file transfer between 32-bit systems and 16-bit systems.

FastLynx does have a DOS slave. Read the docs of FastLynx for more details. Moreover, You can get a copy of FastLynx 2.01 for DOS for free if you have a valid licence of FastLynx 3.x for Win32.
For more DOS compabilitiy, you can convert your WinXP partition from NTFS to FAT32 without data loss via some well-known partition tools such as PQMagic.

FastLynx 3.3 does indeed come with both DOS & Linux Slave Programs, which support Long File Names "Quote" FastLynx 3.3 DOS slave now provides long file name support when running in an operating system environment that supports long file names
For full details read:
http://www.sewelldev.com/DosSlave.asp
As Wengier points out FastLynx also comes with FastLynx for DOS v2.01 Free of Charge.
You can download the earlier v2.0 from my PowerLoad Resource Site 'Free of Charge' with the full agreement of Sewell Developments @
http://www.oldstuff.myagora.net/powerload/fastlynx.htm
This program is still Copyright and NOT Freeware, and the download agreement is from this URL only.

you can do DCC in XP>WFWG, Theres a trick to get Windows XP into using NetBUI, so just setup an incoming connection in Windows XP, then use Remote Access in Windows For Workgroups.

Thankyou Warpster any more info on RAS to XP?
Is this what you meant?
http://www.kime.net/directcc/dccnt40.htm
http://support.microsoft.com/default.aspx?scid=kb;en-us;301041

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |