kirkspragg wrote to All <=-
Soldering 12 wires from 3 different multi-core cables into the DB25
plugs was a bit of a hassle & with three runs of cable between the
plugs. The cables barely fit in the plug housing -but they did fit
with some light encouragement. I just tested it out & it works!
My first IT job had me soldering 100 DB25s onto some kind of shielded cable, forget what type. It was a pain, but at least it was one cable per connector!
That would have made it a bit easier, did you have a decent soldering setup to help you hold the connector & cable in place while soldering together?
So i got round to putting together the 5m long laplink parallel port data transfer cable.
I just tested it out & it works!
Getting around 20KB/s between dosbox running on my main PC and my 386DX40 & I think that a reasonably speed to get form the old standard parallel port in my 386, I'm stoked!
What transfer software are you using? Back in the day, we used a package called "FastLynx", it could get around a megabit of throughport between 486es, using a standard LapLink parallel cable. I have to assume using some form of compression?
Oh that so cool to hear!So i got round to putting together the 5m long laplink parallel port da transfer cable.
I just tested it out & it works!
I just wanted to let you know that you're my personal hero :)
BobW
I think that a reasonably speed to get form the old standard parallel in my 386, I'm stoked!
Hell yeah!
What transfer software are you using? Back in the day, we used a package called "FastLynx", it could get around a megabit of throughport between 486es, using a standard LapLink parallel cable. I have to assume using some form of compression?
TLDR; Nope. The highest best rate that doesn't cause failures or crash the com port is 9600 baud. Turns out the UART in the multi-io card is a 16450 and so just can't do any better.
What transfer software are you using? Back in the day, we used a package called "FastLynx", it could get around a megabit of throughport between 486es, using a standard LapLink parallel cable. I have to assume using some form of compression?
Yea I'm using FastLynx. My past experience with laplink hasn't been so great as it tends to just die on long running transfers. Fastlynx on the other hand seems quite stable.
Eugh... mutli-I/O cards with 16450 UARTs really spoiled my day a few
times back in the 90s. I (486SX-25 with 16550) used to play Duke 3D with my brother (486DX2-66 with 16450) over serial and it would regularly crash. Always my brother's computer pulled it down.
The intrusive thoughts finally got the better of me so I DOSBox'd two copies of LapLink3 and sniffed the traffic going between them. I don't understand all the messages yet but it doesn't look ridiculously complicated - if I ever get the free time I could probably write an implementation of it for my Acorn, which would make copying files back
and forth much easier. I would need to mangle file names (Acorn allows longer filenames, uses . as a directory separator and has file type as a file system attribute) but it would make a fun project.
I've never tried FastLynx, a couple of people have told me it's better, though.
Well if you do get round to making an implementation for Acorn, I'm sure the folks here would be interested so let us know if you do. It would be a pretty cool project.
I constantly hear complaints about unreliable transfers on Laplink - I wonder if there's an element of emulation issues because I used to constantly send stuff between 386 & 486 laptops, probably a 286 desktop,
I don't remember ever having a single failure.
I'll do more testing :)
... Hear no evil, speak no evil, C:\NOEVIL
Must be dosbox. Or maybe nostalgia has me remembering things as better than they were....
Must be dosbox. Or maybe nostalgia has me remembering things as better than they were....
I would check it against another VM like VirtualBox of 86box. That'll tell if it's an emulation or host issue.
I would check it against another VM like VirtualBox of 86box. That'll tell if it's an emulation or host issue.
... He's one bit short of a byte.
Nice to see we are on the same page.... He's one bit short of a byte.
Word!
Sysop: | smooth0401 |
---|---|
Location: | New Providence, NJ |
Users: | 6 |
Nodes: | 4 (0 / 4) |
Uptime: | 86:07:15 |
Calls: | 319 |
Files: | 566 |
D/L today: |
11 files (11,973K bytes) |
Messages: | 52,235 |