IBM System/36 5364 PC

[peclark]

My first post here

I wanted to say a huge "Thank You!" to @NeXT for the blog post on how to recover unknown userids and passwords on the System/36. I've been working on getting mine up and running, and your blog post worked perfectly for me - I can confirm the process does work on the 5364. I now have the system up and running and working with the PC as the console, as well as a 5291 Terminal (that still needs considerable cleanup and probably some new capacitors). The power supply in the IBM PC that acts as the "control panel" and terminal for this "Baby 36" died, so the PC is looking a little disheveled in the picture below. I'm running the PC Connection software off a gotek with flashfloppy. One interesting thing I ran into was if I was booting under DOS 6.22 the PC connection program would hang when trying to initiate the connection, but if I boot under DOS 3.3, it seems to work fine. If anyone is looking to replace a missing 62 pin cable that goes between the PC and the 5364, I found you can buy them on Amazon (I almost couldn't believe it). https://a.co/d/8z0KANU

My next goals for the system are to see if I can edit/compile/run a cobol program, sill learning the commands and structure of the system. Very similar to the AS/400, and a little similar to IBM 370 mainframe ( my early programming experience was on TSO/ISPF on MVS )

Thanks again @NeXT - Really appreciate you taking the time to document the process, and create the javascript decoder. I'm pretty sure I'd have never been able to get logged into this system without it.

Pete

 

[NeXT]

Oh nice! Well that answers that question. Never worked on one myself so I didn't know how you would access the operator's console.

 

[peclark]

My goal of getting a COBOL program created, compiled, and executing has hit a bit of a snag. Turns out COBOL is not installed on my machine, only RPG. I have the install media (5.25 floppy) for COBOL and BASIC), so I've started down the path of getting these features added to my machine.

I've run into a problem I'm struggling with - the built in 5.25 floppy drive errors out with a "Drive not Ready, Intervention required" message. I've checked the drive, and it's mechanically functional, head moves, spindle motor turns fine.

I tried adding a gotek to replace this drive, using IMDs (converted to HFEs) of the install media, but I'm getting the same "Drive not Ready..." message. I'm a little worried that there may be a fault with the floppy controller circuit on the 5364. Just curious if anyone else has run into a similar issue?

 

[NeXT]

Do you know if the RDY signal from the floppy drive is making it to the controller?

 

[peclark]

Do you know if the RDY signal from the floppy drive is making it to the controller?

I'm not sure - the floppy drive appears to be proprietary in this model, and the physical floppy, and gotek have the same issue. I'm thinking it's either a problem with the cable, the controller (built into the motherboard), or perhaps some kind of config issue in the OS for the floppy drive.

When I try to access the floppy from the OS, the drive spins up, and the head will move a bit. Looking at the gotek, it's stepping a couple tracks and then gives up with the drive not ready...

I'm not positive which pin the System36 is looking at for RDY. Guessing pin2, but can't find anything that makes me sure...

I think my next step might be to try a different cable to eliminate that.

 

[peclark]

I'm not sure - the floppy drive appears to be proprietary in this model, and the physical floppy, and gotek have the same issue. I'm thinking it's either a problem with the cable, the controller (built into the motherboard), or perhaps some kind of config issue in the OS for the floppy drive.

When I try to access the floppy from the OS, the drive spins up, and the head will move a bit. Looking at the gotek, it's stepping a couple tracks and then gives up with the drive not ready...

I'm not positive which pin the System36 is looking at for RDY. Guessing pin2, but can't find anything that makes me sure...

I think my next step might be to try a different cable to eliminate that.

With the help of a new, and very generous, friend from the forum here, I was able to replace my bad floppy drive, and the new floppy works great. The new floppy drive is a YE Data YD-380 Type 1718. Thank you very much (you know who you are !

I was able to upgrade my 5364 from V4 to V5 M1 SSP, along w/the program products that were already installed. I was able able to image the drives using David Gesswein MFM Emulator, and successfully run the 5364 from the MFM emulator, using the images from the physical drives. I'll make a separate post about that.

I'm still having challenges getting COBOL installed, and will make a separate post about that as well.

Thanks everyone for the help!


Pete
.