Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site sfmin.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!mhuxv!mhuxh!mhuxj!mhuxn!mhuxm!sftig!sfmin!jeffj
From: jeffj@sfmin.UUCP (J.S.Jonas)
Newsgroups: net.micro.cpm
Subject: May I boot from drive B.  Please? Pretty please?
Message-ID: <631@sfmin.UUCP>
Date: Wed, 18-Dec-85 11:26:02 EST
Article-I.D.: sfmin.631
Posted: Wed Dec 18 11:26:02 1985
Date-Received: Fri, 20-Dec-85 01:33:29 EST
Distribution: net
Organization: AT&T Bell Laboratories, Summit N.J.
Lines: 22

[when in doubt, pip it!]

	When CP/M boots, it considers the drive that it booted from A:
and starts with with the A> prompt.  Can I corece it into believing
it booted from B:, and how?
	One may ask "why", and I haven't a complete answer.  I am
puzzling over how to handle a system with a SSDD and a DSDD drive.
Normally I boot from the SSDD, but if that boot is bad, I would want to
boot from the DSDD.  Unfortunately, the boot ROM looks only for device 0
so I have to change the drive addresses and will probably confuse
CP/M (watta you mean drive 0 is single sided? It was double sided when
I booted!).

	My solution for now is to logically define the double sided drive
as B: double sided and D: single sided.  This way, I can copy
A: (the single sided drive) to D: and use the disk in drive A:.
I just have to keep enough backups of the single sided system disk
to keep out of trouble.

	Thanks in advance.
				Jeff 'how did I get into this' Skot
				{ihnp4 | allegra | mcnc} attunix ! jeffj