XDOS Boot to STDC Not working.

19 views
Skip to first unread message

rlm2667

unread,
May 16, 2025, 3:09:51 PMMay 16
to Cromemco
I find, fairly suddenly, my XXU with XDOS 2.04, will not boot directly to the STDC drive(s). Unix or Cromix. Throws error.

XDOS  version 02.04
Preparing to boot STDC 32 - type ESC to abort
Address:  Memory test by 16k blocks
00000000    +++++++++++++++++++++++++++++++++++++
Co-processor  test OK
STDC ERROR: command 14 Stat e1  05ff
;

If I boot to a floppy with Cromix root set to 6  32, it boots all the way no problem. Once booted to std32, boot from the command line works fine. readall has no problem reading the drive from track 0 on. No errors. wboot has no problems writing the boot track and inithard reads the drive description from track 0 no problem. 

Trying bst1f to boot Unix results in the same response and error.

I'm using Dave Gesswein's ST506 emulator. I've tried 2 different STDC's and tested the emulator in a system 400  with a 31.68 drive image with no issues. 

setting the 41.72 Cromix image to drive 0 on the emulator and trying to boot to st0 has the same result. I tried a backup of the 41.72 image from some time ago also with the same result.

If I try to select st0 or st32 in XDOS I get the same error. 

It seems the rom has flipped a bit or something.

Any thoughts or suggestions would be appreciated.

Richard M

Jay Cotton

unread,
May 16, 2025, 5:11:53 PMMay 16
to Cromemco
I have seen that myself.  I found power cycle required to clear it.
Also run TX and test all the ram in the long test version.

Also try 
:STD
:RA

read all the disk sectors.

jc

Richard Muse

unread,
May 16, 2025, 5:50:21 PMMay 16
to crom...@googlegroups.com

tx: yields no errors.

std: STDC ERROR: command 14 Stat e1 05ff

ra: No drive selected

XDOS won't select the drive so ra can't check it. It appears because it can't read the drive information on track 0. That's just a guess because I don't know what the command 14, Stat e1 or 05ff mean.

I do know that if the drive isn't connected I get 07ff, so it does know there is a drive out there.

Cromix has no trouble reading all of the drive????

I'll steal the control cable from another machine and try that. Just don't know how it would work normally once booted from a floppy if the control cable has a problem though.

RM

--
You received this message because you are subscribed to the Google Groups "Cromemco" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cromemco+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/cromemco/5a8a2adb-cc71-459a-a129-928b0ca7792bn%40googlegroups.com.

Mike Stein

unread,
May 18, 2025, 1:20:55 PMMay 18
to crom...@googlegroups.com
Sure sounds like a problem reading track 0 and the boot file, but I'd expect mounting and booting from a floppy to also have trouble reading the disk info. FWIW I've had issues booting from drive1; just got back home after a lengthy absence so time to fire up my system and fool around a bit

If you really think it's a ROM problem here's a dump in various formats

Good luck!

m

XDOS204.zip

Richard Muse

unread,
May 18, 2025, 2:29:45 PMMay 18
to crom...@googlegroups.com

Thanks Mike. According to the XDOS instructions XDOS does a crc check when it boots and flashes a code if it fails. Then copies itself to memory sort of like Rdos. No lights flashing so I'm probably wrong about that.

I've tried a spare 34pin cable but I'm going to steal one from one of the other systems and try that. Not sure how a bad cable would work from Cromix but not XDOS but????

R

Reply all
Reply to author
Forward
0 new messages