Where are you located, Mike?
> On Nov 19, 2024, at 1:31 PM, Michael Brutman <[email protected]> wrote:
>
> (Trimming the message history ...)
>
> So here is my current state:
>
> * The "twist" connector that swapped the bottom row of pins with the top row
> of pins was wrong for me, as it was in the other thread. The male pins
> should have been straight through - top-to-top and bottom-to-bottom. I
> figured this out last night and rewired the twist connector to correct it, as
> the other person had done. I've buzzed the twist connector and everything is
> there. The IDE cable is new and it is secure on the DVI.
>
> * My Model 100 adapter (unused so far) seems to also be incorrectly
> assembled. I have an email to Gregory about that. (This is in addition to
> the incorrect twist adapter.)
>
> * The worst thing that might have happened is the top row was swapped with
> the bottom row. Which for the most part is safe, as you (Brian) note. There
> are one or two pins I'm worried about that I need to do more research on.
>
>
> Both M102s have the same general problem now. I power them on first. I
> power on the DVI. The DVI boots, loads from the floppy, and displays the
> copyright message. I wait a few seconds, then use the reset button on the
> M102. The DVI responds and starts to run the disk drive, presumably trying
> to transfer disk BASIC to the M102. This never completes. No amount of
> power off-on, reset, or cold start helps it.
>
> The DVI will run the disk light a second or two, pause a second or two, and
> then try again. If I press the BREAK button early (maybe Shift Break?) I can
> get control again from the keyboard but disk BASIC is not loaded. If I let
> the cycle repeat too many times the machine needs a cold restart.
>
> At this point I have one or more problems:
>
> * The M102s have some damage because I did the same thing to both of them. I
> can't tell. Maybe it's time to get the o-scope out and look at the
> potentially damaged signal pins to see what they are doing.
>
> * The cable is still wrong, but I think I have it correct this time after
> examining everything for myself.
>
> * The DVI might have a fault. Unlikely given its condition and behavior so
> far.
>
> * The disk I wrote might be crap. I used Teledisk v2.16 on a 386 PC with a
> real floppy controller. It's good enough to load the initial sectors, but I
> can't verify the rest of the disk. I might be loading bad data into the DVI
> buffers and passing it onto the M102, and that could be causing the crash.
> But there is no easy way to prove or disprove that.
>
> * The M102s have other faults that are unrelated to all of this. (They have
> never had their capacitors replaced.)
>
>
> At this point I'd like to find a working DVI setup in the region so I can put
> my M102s on it to see if they are working correctly - I really want to ensure
> they weren't damaged with the incorrect cabling. If they are good then I'm
> no worse off than I was a few days ago when I started this project.
>
>
> -Mike
>
