Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Hi again pals, please help me in these topics:
1) How i can make a paralell db-25 data transfer cable?
2)interlnk and intersvr will work if i connect my old dos622/wfwg311 laptop to a desktop pc with win 98 or xp? it will recognize the drives for data interchange?
3)Is there another 3.1 software to data transfer?
4) The serial port will work the same as paralell port?
Thanks.
Takeru

get a program called drivecopy.
it comes with the laplink cable to connect to the ppl ports.
the software will run in dos, windows.
i love it

Thanks KKK, IŽve taking a look to the drivecopy but is a little bit expensed for me, so i just wanna use my "freeware" interlnk.exe of my dos directory and get the information to make my own LPT transfer cable, so i have an idea: if I start the both computers, the laptop (dos622) and the desktop pc (win xp) with a MS-DOS 6.22 boot disk and execute the interlnk and intersrv stuff and hook up them with my "home made" db-25 cable..... it will work? please helllp.
Thanks for all...
Takeru

To connect your DOS 6.22 and Windows 98:
On DOS 6.22 machine:
Add this line to C:\CONFIG.SYS:
DEVICE=C:\DOS\INTERLNK.exe
On Windows 98 machine:
Boot to DOS Mode (F8 or hold CONTROL key for menu), then enter this at the C: prompt:
INTERSVR
(make sure you put the INTERSVR.exe file on the current directory or go to the location of the file first, such as "A:", then "INTERSVR")
Now, reboot the DOS 6.22 machine, and it should load the INTERLNK file and you should see the drives being shared.
Yes, I have used serial AND parallel cables successfully with INTERLNK/INTERSVR, without having to make a distinction to the software.
Good luck.

Thank you KKK, SkipCox and C_Legend for the good tips, i'll try this today, and i let you know the results right here.
Takeru

I had a thought. You may have problems with FAT32 file systems (Windows 98) and/or long filenames, and therefore if you happen to have a FAT16 filesystem on the 98 machine, you may want to use it to copy your files across (copy from FAT32 to FAT16 first, if the files needed to copy are on FAT32 filesystem). INTERLNK/INTERSVR were out before FAT32 and long filenames, therefore there may be incompatibilities. Good luck.

3)Is there another 3.1 software to data transfer?you should beable to use direct cable connection and have a network connection between the 2 computers using paralell port able to do anything a newwork can but slower
http://www.kime.net/directcc/dccras31.htm

For transfering files between FAT32 drives as well as FAT12/16 drives, you SHOULD use MS-DOS 7.10 + FastLynx 2.01 instead of MS-DOS 6.22 + INTERLNK/INTERSVR, because the latter is totally FAT32 incompatible.

Good tip fron Wengier I found that one out the hard way :)
in the last post I forgot to add ..
it will decribe how to link Windows 3.11 to Windows 95 with a (serial)Null modem with full instructions and pictures you will probably have to change some of the options for parallel.
The setup instructions should also work with 98

FastLynx 2.01 supports FAT32 Drives but not Long File Names!
Extract from FastLynx 2.01 Notes:
Support for FAT32 drives in Windows 95 was added. FastLynx 2.0 had a problem interpreting the amount of free space on drives larger than 2 GB, and would sometimes erroneously refuse to transfer a file because it thought there was not enough free space left. Version 2.01 overcomes this problem. Long file names are still not supported, however (they get truncated during the transfer).
The cheapest retail package I know of is FastLynx 3.3 for Windows 3.1 to XP (With version 2.01 for DOS included) Note that it will transfer files between Windows 3.1 to XP
http://www.computertimes.com/mar02edchoicefastlynx3.htm (Recommends earlier v3.2)
or
http://www.sewelldev.com/FastLynx3.asp
PowerLoad hosts FastLynx 2.0 for DOS Free of charge with the full consent of Sewell Developments as a service to DOS Users.

C_Legend: I had a thought. You may have problems with FAT32 file systems.....
Yes, you all right, my very old laptop doesnŽt recognice the drives in the other machine (fat32/win98), i not tried yet the fastlink but iŽll try today. I made a null modem cable of two old mouse cables DB9 to DB9 as the pinouts conections as well, or... must I make a paralell null modem cable to work? A tip, Long filenames doesnŽt interesting for me, i only want to hook up my fat16 laptop to my fat32 desktop PC just for transfer or install the WFWG311 or OFFICE42 without the wasting of time with the diskettes, just for it and to make a backup of all my files in case of an accidentally formatting.
Help me plz. fat16-nullmodemcable-fat32 (or)
win31-nullmodemcable-win98 (gonna be?)
Takeru

C Legend (and everyone else), the problem here is very easily solved. Yes, Interlnk/intersvr has problems reading a fat32. Therefore, just reverse the procedure. Copy interlnk.exe to your Win98 machine ( i suggest c:\dos, create it if not exit) then add the line:
c:\dos\interlnk.exe
to your config.sys in the Win98 system then reboot to load it. This system is now the client. You will have to rem out or remove that line later if you don't want interlnk to load after you are done.
Now on the laptop (running wfw 3.11 on a fat16), from Dos or in a Dos box run the command intersvr. This will turn the laptop into the server intead of the Desktop, thus this will be the one being read (fat16, no problems)! To move files, you use the desktop to input the commands (works well in windows, where you will see the drives from the laptop). That way, no fat32 problems!
HTH.
Lightspeed.

Yes, give that a try. The reason I didn't mention that (and the reason I suggested the way that I did originally) was that I was concerned that loading INTERLNK.exe on Windows 98 would return "incorrect DOS version", as this is what happens on my DR DOS 6 machine. INTERSVR, on the other hand, didn't have this limitation. Thanks, and good luck.

Interlnk works fine in 9x and ME, but i haven't tested it yet in XP.
For more info about networking, see my page under that header, there is a very good page there by Powerload about how to make your own DTC (also known as laplink cable), as well as a few programs to download.
Have fun!!!
Lightspeed :).

Ok ok, all is fine, the Ligthspeed method works really well, thanks, i'm learning a lot with you guys, hope i can help someone in the future.
But... Here goes a really silly question:
Is possible to connect a cd rom drive to a parallel or serial port?..... just to avoid the intelnk stuff.... or another way to connect a Cd rom drive to my very old laptop, sorry if i botter you, next step is to buy a good pc.
Takeru

"Is possible to connect a cd rom drive to a parallel or serial port?"
parallel cdrom yes its posible you want a microsolution backpack cdrom drive usually go for around Ł28 on ebay
Couldnt you get the serial transfer to work or was you just after a permanent file access ??
you could always get a laptop IDE to desktop IDE converter and plug it into your desktop PC put the files on and stick it back in your laptop

This is another advantage of using the desktop as the client (local computer) and the laptop as the server (remote). Interlnk/intersvr cannot read a CD-ROM on a remote computer. If your laptop has no CD drive, your desktop certainly does, and being the local machine, it means you can drag and drop any file in Windows explorer from your local CD drive onto the remote laptop drive to send files from a CD to it. Very useful to send installation files for example.
Of course if you are looking for a more permanent solution, what Play3r makes sense, get yourself an external CD unit and make sure it is compatible with ser/par (not just usb).
Lightspeed.

Thank you guys for your advices.
I have an announcement for you, Takeru (user name) is dead, now IŽll be known as Mstr (like my email) and the reason is for my comming soon WFWG311/DOS622 resources page in english and spanish versions.
Say good bye to..... Takeru

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

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