Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!europa.eng.gtefsd.com!MathWorks.Com!yeshua.marcam.com!zip.eecs.umich.edu!newsxfer.itd.umich.edu!nntp.cs.ubc.ca!unixg.ubc.ca!news.bc.net!newsserver.sfu.ca!sfu.ca!vanepp
From: vanepp@fraser.sfu.ca (Peter Van Epp)
Newsgroups: comp.os.386bsd.development
Subject: Re: [FreeBSD] patch to allow mounting of DOS drives
Date: 24 Aug 94 00:30:57 GMT
Organization: Simon Fraser University
Lines: 44
Message-ID: <vanepp.777688257@sfu.ca>
References: <32uvui$dov@Venus.mcs.com> <334mjf$1ku@euterpe.owl.de> <CuxDFB.1nv@tfs.com> <33bbeo$4q@rivendell.apana.org.au> <Cuyonp.Mq5@tfs.com> <vanepp.777616954@sfu.ca> <Cuzq3L.23nt@austin.ibm.com>
NNTP-Posting-Host: fraser.sfu.ca
radha@austin.ibm.com (Radha Krishnan) writes:
... (deleted to keep the damn news poster happy! I can feel an include line
lobotomy of the news poster coming on ...)
>I didn't have any problem building the original unmodified patch. However,
>it still didn't work for me with two SCSIs. Julian is looking in that.
>I'd really be curious if your attempt at two disk machines worked? If so
>could you please send me you fdisk and disklabel outputs??
>P.S Thanks for your help reg Bootblock installation for booting off from sd1.
You are welcome.
>> >! if ((bp->b_un.b_addr[510] != 0x55)
>> >! ||(bp->b_un.b_addr[511] != 0xaa)) {
>>
>> needs to be:
>>
>> >! if ((bp->b_un.b_addr[510] != (char) 0x55)
>> >! ||(bp->b_un.b_addr[511] != (char) 0xaa)) {
>>
All the patches compile, without the cast, I (on FreeBSD1.5.1) get
a compiler warning that the test always evaluates to true (presumably because
caddr_t is *char and the compiler is taking 0xaa as unsigned char and not
sign extending), and indeed it dies a with the no Fdisk warning errors.
So far I have had no joy on the boot from a second disk with any patch,
but printfs at the above line in the code indicate that the signature values
(in fact I believe the entire boot block) is 0s (yet without the fix it manages
to boot correctly). I am still looking at this. I am just about to go home
where I have one machine with a single disk that works with the above patch
and a second with 2 disks (and FreeBSD on the second disk) that doesn't.
Has anyone else (with possibly a more conventional setup i.e FreeBSD
on drive 0 and DOS on drive1) had any success? I believe my problem is likely
as a result of my changes to boot from the second disk with bootmenu (although
I have so far found nothing wrong).
Peter Van Epp / Operations and Technical Support
Simon Fraser University, Burnaby, B.C. Canada