• Please review our updated Terms and Rules here

Advanced Digital Corporation Super Six TurboDOS and TurboDOS x86 PC - can they communicate ?

retrogear

Veteran Member
Joined
Jan 29, 2014
Messages
1,040
Location
Minnesota
Still no joy with rev 4. Everything is good on the ADC side, when I do a DIR to the remote PC drive, it pulses the transmit line and then gives 'network error'. If I connect it to a modem it transmits/receives like crazy trying to make a circuit connection. The PC side is a dead horse. I assembled the new UART sources and linked them in but the pc just locks up when osmaster runs. Like you told me, TurboDOS for PC was a science experiment at best. I'm flunking this science class so far :)

Larry G
 

retrogear

Veteran Member
Joined
Jan 29, 2014
Messages
1,040
Location
Minnesota
Aha - reading the LAN-PC control manual Aug 84 p51 SIOA needs to be set to the COM1 port address (0x03F8).
I have it set to (0x00) which disables it.

Larry G
 

retrogear

Veteran Member
Joined
Jan 29, 2014
Messages
1,040
Location
Minnesota
When I use the SIOIPC module, if I set SIOA = (0x03F8) then when booted, I get an 0C> prompt but no response to keyboard. I see no changes in the lights on my serial breakout box either. I have no clue why this would kill the keyboard ? Leaving it at (0x00) has an active command prompt but attempting a remote drive access just locks like a dead serial port. Since that module
had a different serial# makes me think it was written for the LAN-PC card and not a regular PC serial card but the description in the manual sure sounded like it would.

Larry G
 

new_castle_j

Experienced Member
Joined
Dec 3, 2011
Messages
283
Location
Texas, USA
Hmmm, since the SIOIPC driver was written for the IBM PC/XT 8250 chip, could there be an incompatibility with your 386 PC? I'm not sure what else to try, perhaps just need to meditate on the situation for a while.
 

retrogear

Veteran Member
Joined
Jan 29, 2014
Messages
1,040
Location
Minnesota
I repeated the experiment on my IBM XT with a different ancient serial card for the XT with the same results. I think that SIOIPC driver is bogus.
All examples I've seen in manuals have that driver rem'd out. I would sure like to get that uart driver source to work
 

retrogear

Veteran Member
Joined
Jan 29, 2014
Messages
1,040
Location
Minnesota
I had a setback when the hard drive on the ADC decided to crash. It was reporting a trashed track 3. I pulled the drive (Seagate ST-225) and connected to an MFM controller on a PC and formatted / confirmed the drive is perfect. I put it
back in the ADC connected to the Monitor Dynamics HD1013 I've been using, spaced the card out in the S100 frame with a cooling fan on it then went through the procedure in the ICM TurboDOS Configuration Manual June 86
starting on page 3-19. Yes I found a more detailed procedure in this manual vs the HD1013 technical manual itself. This time I paid attention to the last paragraph on page 3-21 which states if you don't have a sequencing power supply
which the 12v and 5v supply is turned off first then a second later the S100 gets turned off you could trash the directory of the hard drive. Well crap, the directory is stored on track 3 !!! I have a separate power supply for the hard drive
which I'd always turned off LAST !!! If not sequenced, the manual recommends assembling HALT.MAC and running that each time before powering down. I'll do that from now on. With all the testing I've been doing trying to get the serial
network to fly, I've been power cycling quite a bit and tempting fate which caught up to me. It pays to RTFM.

Larry G
 

retrogear

Veteran Member
Joined
Jan 29, 2014
Messages
1,040
Location
Minnesota
I still haven't come up with a solution to network two TurboDOS systems via serial port. I revisited the work done by Mario Viaro porting TurboDOS to Z80 SIM and Joe Moore porting it to his ZEMU emulator.
Joe got ZEMU to connect master/slave via TCP/IP and I just got two Win98 boxes talking TurboDOS to each other. I did this back in 2015 as well. I see Joe also wrote a serial driver EMUSER so I'm going to see if I can get CKTSER
to connect thru his EMUSER to my real ADC S6 S-100 hardware which I'm sure is trying to connect via serial port. Here's a photo of my ZEMU TurboDOS connection between PC's with TCP/IP. The ADC S6 hardware is off to the left side out of photo. I see Joe gave me credit for helping him upgrade to TurboDOS 1.43 - Larry Greene
ZEMU TurboDOS network.JPG
 

retrogear

Veteran Member
Joined
Jan 29, 2014
Messages
1,040
Location
Minnesota
Well, I'm halfway there. I now have the ADC S6 connected via a serial port to the Win 98 box running ZEMU emulator. I was able to use 19,200 baud. ADC S6 drive F: is mapped to the
ZEMU drive A: I am not able to do visa versa yet. On the ADC doing DIR F:*.* will show a directory of A: on the other ZEMU PC via com ports. Still a work in progress trying to get TurboDOS PC hardware
to respond to the com port directly without an emulator.
tdos remote.JPGtdos remote zemu.JPG
 

retrogear

Veteran Member
Joined
Jan 29, 2014
Messages
1,040
Location
Minnesota
Now it appears that the disk assignment table of the remote drive has to be defined locally. I can type the file contents of the remote files but they are wrong
since the DPB's don't match. The ZEMU disk definition is PC1440 but the ADC local drive is currently 8" DSDD. It does report an error if the filename is wrong but not the contents.

Larry G
 
Top