HDTenEightyP/NetNews huggingface dataset:
From: eoahmad@ntuix.ntu.ac.sg (Othman Ahmad)
Subject: Re: help wanted with disappearing disklabel
Organization: Nanyang Technological University - Singapore
X-Newsreader: Tin 1.1 PL4
Date: Wed, 26 Aug 1992 03:49:00 GMT

ado@bigcomm.gun.de (Christoph Adomeit) writes:
: Hi freaks,
: 
: from what I see on the 2 floppys I like 386bsd 0.1 very much.
: I can install it on disk (together with MSDOS), means the install
: program runs fine.
: Afterwards I can't boot from the hd. (IDE ST1239)
: It boots, detects all the hardware and then reboots over and over
: with an error I cant read.
: I already tried the new bootwd posted here, and also made sure that
: partitions do start at cylinder boundaries.(No star using "disklabel").
: Booting up the fixit-floppy shows that the "disklabel" is completely
: mad. The number of cylinders is more than 1200 instead of 769,
: the rpm and interleave are 0. I can reedit the disklabel and
: correct it, but after the next boot it's the same problem.
: 
: When I remove my DOS-Partition and install on the entire drive, It
: works perfectly !!!

I had the same problems. My attempts at manual installation and trying to
install DOS partitions failed because I cannot install DOS at the first 
partition.
	386bsd tries to use the first partition as the root device even when
it is labelled as wd0c .
	I do not know how the root device is chosen.

My solution is just to install 386bsd for the whole drive.

Another option which I may explore is to try install DOS at other partitions
other than the first cyclinders.


--
Othman bin Ahmad, School of EEE,
Nanyang Technological University, Singapore 2263.
Internet Email: eoahmad@ntuix.ntu.ac.sg
Bitnet Email: eoahmad@ntuvax.bitnet

Newsgroups: comp.unix.bsd
From: colin@marsh.cs.curtin.edu.au (Colin Manning)
Subject: Re: What is 386BSD ?
Organization: Curtin University of Technology
Date: Thu, 3 Sep 1992 01:26:33 GMT

jas37876@uxa.cso.uiuc.edu (John A. Slagel) writes:


>    I know very little about 386BSD. I saw some articles in Dr Dobbs about
>    porting Unix to 386, and I guess we can get it free, even the source 
>    code. That's all I know about it.

>    1. Is it really free ? 
	Well...  the Jolitz's have put a lot of work into it, and have asked
for a donation if you can afford it.
>    2. Where can I get it ? (I can FTP)
                agate.berkeley.edu              128.32.136.1
                gatekeeper.dec.com              16.1.0.2
                MATH.ORST.EDU                   128.193.16.60
                UTKUX1.UTK.EDU                  128.169.200.67
                terminator.cc.umich.edu         141.211.164.8

	These addresses are from the FAQ

Just to name a few
>    3. How much disk space for:
>	*kernel
>	*X
>	*source to kernel
>	*source to X
        Binary only:    49 M (30 disk, 5 swap, 14 extraction)
        Source:         125 M (49 bin, 37 disk, +6 extraction, 25 recompile)
        User software:  +51 M

	X Binaries require about 61 Meg (?)
	I don't know about the sources.

>    4. I have 386-33, 130meg HD, 4meg RAM, ET4000 card, microsoft mouse.
>       (no 387) will this config work?
	Sounds like it should
>    5. How good does it work?
	Great.
>    6. Is there free developement kit, C, C++, libraries,etc..?

	GNU C & C++ & libs, etc

>    Thanks for all information. 
>-- 
>------------------------------------------------------------------------
> John A. Slagel     "My old man used to tell me, before he left this
> j-slagel1@uiuc.edu  shitty world, never chase buses or women- you
>                     always get left behind." -The Marlboro Man
--
Colin [colin@cs.curtin.edu.au]

"Knowledge is not knowing all the answers, but knowing where to find them."
                                                                  -anon.
Newsgroups: comp.unix.bsd
From: eoahmad@ntuix.ntu.ac.sg (Othman Ahmad)
Subject: Re: Help with installing srcdist in 386bsd
Organization: Nanyang Technological University - Singapore
X-Newsreader: Tin 1.1 PL4
Date: Fri, 28 Aug 1992 02:36:35 GMT

cl45@cunixf.cc.columbia.edu (Ching-Tse Liu) writes:
: Hi,
: 
: 	I have problem installing the source distribution. Right after
: I installed the binaries distribution, I typed "rm bin01.*" then "
: loadfd". Now when it came to src01.37, the system stopped and refused
: to copy anymore files and didn't respond to control-c. I had no choice
: but to reboot. Of course it came up with the content of /tmp cleared.
: What did I do wrong ? I tried this twice with the same problem.
: 	Is it possible to install the source with the binaries installed?
: Or do I have to start all over ? Any help will be greatly appreciated.
: 
You may be running out of disk space.
You need to be selective in recovering src files. I recommend that you only
recover sys.386bsd. See my and other notes on this.
: 

--
Othman bin Ahmad, School of EEE,
Nanyang Technological University, Singapore 2263.
Internet Email: eoahmad@ntuix.ntu.ac.sg
Bitnet Email: eoahmad@ntuvax.bitnet
From: brtmac@maverick.ksu.ksu.edu (Brett McCoy)
Newsgroups: comp.unix.bsd
Subject: Re: Kernel rebuild - load error?
Date: 29 Aug 92 23:25:41 GMT
Article-I.D.: maverick.BRTMAC.92Aug29162542
	<STARK.92Aug29073021@sbstark.cs.sunysb.edu>
Organization: Kansas State University
NNTP-Posting-Host: maverick.ksu.ksu.edu
In-reply-to: stark@cs.sunysb.edu's message of Sat, 29 Aug 1992 12:30:21 GMT

In article <STARK.92Aug29073021@sbstark.cs.sunysb.edu> stark@cs.sunysb.edu (Gene Stark) writes:

>>     I am trying to rebuild my kernel to change it so that my 3c503 ethernet
>>adapter talks out its AUI port instead of the thinnet port.  (Thanks for the
>...
>>shortly, I get the error:
>>
>>  init_main.o: undefined symbol _version refrenced from text segment
>>  *** error code 1
>
>I got this, too, on my first attempt to recompile the kernel.
>The problem is that "init_main.c" references the "version" string, but
>the "config" program does not set up the file "vers.c" in your
>compile directory.  If you look at the GENERICISA compile directory,
>you will find files "version" and "vers.c", and you will see that the
>Makefile includes "vers.o" at the end of the list of files to be loaded.
>
>Since I was just hacking anyway, I just copied "vers.c" from the GENERICISA
>directory and edited my Makefile.  This is undoubtedly not the correct
>solution, because if I re"config" the changes to the Makefile are reverted.
>However, it enables me to load the system.  I'd be happy to hear about
>the correct fix.

Look in mirrors4/386bsd/386bsd-0.1/unofficial/Makefile.i386.cgd on
wuarchive.wustl.edu, or any of the other mirror sites, for the patches
needed to fix this problem.

++Brett;
From: hbj@engr.uark.edu (Bernard Johnson,,,444-8266)
Subject: Re: Colorado Memory Systems tape drive
Keywords: CMJ, Jumbo, DJ-20
Organization: University of Arkansas
Date: Fri, 4 Sep 1992 04:39:55 GMT

hasty@netcom.com (Amancio Hasty Jr) writes:

>Also, you may add that they will not release any technical information
>on their interface!

QIC-40/80 is a standard and is documented.  You can call Quarter Inch Standards
to obtain *free* documentation.  Probably what you are looking for is QIC-117
which describes the command interface.

Bernard Johnson
hbj@engr.uark.edu
Newsgroups: comp.unix.bsd
From: kilroy@mik.uky.edu (Paul S. Kilroy)
Subject: Is runnning BSD feasible??
Organization: University Of Kentucky, Dept. of Math Sciences
Date: Wed, 26 Aug 1992 13:44:03 GMT

Hi all,

	Sorry, I dont know if this is a FAQ so please bear with me...
   I was wondering if running BSD on a 486 with 8 meg of ram on a
   pc in my home is feasible(ie. not too many bugs). I have heard
   mixed reviews about the bugginess of BSD. I would be doing simple
   things such as running X-windows, writting small programs for 
   school(and trying to compile them :)), and other things cs students
   do. Any help is appreciated, please reply in personal mail 

thanks in advance
	Paul
--
                       -Paul   (kilroy@mik.uky.edu)
From: brians@rigel.cs.pdx.edu (Brian Smith)
Newsgroups: comp.unix.bsd
Subject: Re: 386BSD 0.1: trouble with western digital card 8013 EBT
Keywords: 386BSD
Date: 27 Aug 92 16:48:20 GMT
Article-I.D.: pdxgate.6032

news@hp832.informatik.hu-berlin.de (H.Boehme U.Kunitz) writes:

>Hi,

>We installed 386BSD 0.1 on a 386 AT. Everything works fine, but ...
>We tried to use the networking features. It seems that there is
>a software problem. The programm isn't able to read networking packets
>correctly. Following messages are printed:
>reject: 65xxx. (xxx stands for different numbers.)

>We found that in the memory on every second byte is a 0xff.
The problem is most likely that the vga board that you have is 16-bit,
and the memory address that the wd8013 is at is in the same 128K range
as the 16-bit vga memory.  The MMU on the [34]86 believes that the memory
mapped RAM from the wd8013 is 16-bit accessible.  I've had this problem
here at work.

The kludge solution is to put your vga card in a 8-bit slot.

Brian

/---------------------------------------|------------------------------------\
| #include <std/disclaim.h>             | Inet: brians@rigel.cs.pdx.edu      |
| #include <human/erors.h>              |       brians@protools.com          |
|---------------------------------------|------------------------------------|
| Behold the warranty.. the bold print giveth and the fine print taketh away.|
\----------------------------------------------------------------------------/
Newsgroups: comp.unix.bsd
From: tih@barsoom.nhh.no (Tom Ivar Helbekkmo)
Subject: 386BSD: buffer space allocation -- a small bugfix.
Organization: Norwegian School of Economics
Date: Fri, 28 Aug 1992 06:21:48 GMT

Well, I guess it's my turn!  :-)  I'm now seeing the "kmem_map too
small" panic here, when I try to copy a large file (a 1.44Mb floppy
image) from an NFS-mounted device to a local hard disk.  I've tried
making the changes that have been suggested, but that didn't help.
(Sanity check in machdep.c, 500 to 1000 increase in vm_map.h.)

However, while looking at /sys/i386/i386/machdep.c, I discovered a
little bug in it.  (Fixing it hasn't solved my problem, either, but
at least it's a bug!)  Here's what I was looking at:

    /*
     * Determine how many buffers to allocate.
     * Use 10% of memory for the first 2 Meg, 5% of the remaining
     * memory. Insure a minimum of 16 buffers.
     * We allocate 1/2 as many swap buffer headers as file i/o buffers.
     */
    if (bufpages == 0)
            if (physmem < (2 * 1024 * 1024))
                    bufpages = physmem / 10 / CLSIZE;
            else
                    bufpages = ((2 * 1024 * 1024 + physmem) / 20) / CLSIZE;
    if (nbuf == 0) {
            nbuf = bufpages / 2;
            if (nbuf < 16)
                    nbuf = 16;
    }
    freebufspace = bufpages * NBPG;
    if (nswbuf == 0) {
            nswbuf = (nbuf / 2) &~ 1;       /* force even */
            if (nswbuf > 256)
                    nswbuf = 256;           /* sanity */
    }
    valloc(swbuf, struct buf, nswbuf);
    valloc(buf, struct buf, nbuf);

Bill Jolitz suggests a sanity check on the calculation of bufpages,
keeping it at a max of NKMEMCLUSTERS/2.  In my case, that's not the
problem, since the calculation doesn't come out higher than that.
(I only have 8Mb of RAM.)

However:  The comment in the above code says to allocate 10% of the
first 2 Meg, then 5% of whatever remains.  This is *not* what the
code itself does.  Since physmem et al do not count bytes, we're
sort of mixing apples and oranges here, and end up with 10% of the
entire physical memory, no matter what.  The following calculation,
however, does do what the comment says:

    if (bufpages == 0) {
            bufpages = min(physmem, btoc(2*1024*1024)) / 10 / CLSIZE;
            if (physmem > btoc(2*1024*1024))
                    bufpages += (physmem - btoc(2*1024*1024)) / 20 / CLSIZE;
    }

(Actually, I'm not too sure about the "/ CLSIZE", but since CLSIZE is
equal to 1, at least on my machine, it doesn't really matter...  :-))

I still can't copy large files from NFS to UFS disks -- but what the
heck, I'm sure that will come in due time!  :-)

-tih
--
Tom Ivar Helbekkmo, NHH, Bergen, Norway.  Telephone: +47-5-959205
Postmaster for domain nhh.no.   Internet mail: tih@barsoom.nhh.no
Newsgroups: comp.unix.bsd,comp.windows.x
From: liu@cs.sfu.ca (Lixin Liu)
Subject: X386 under 386BSD does not work
Keywords: X386, 386BSD
Organization: CSS, Simon Fraser University, Burnaby, B.C., Canada
Date: Thu, 27 Aug 1992 20:03:28 GMT

Hi, everyone:

After a few days of trying, I can not get X386 working on my 486 machine.
Start with "xinit", I only got into graphics mode twice during the last a
few days and then the system hangs. But most of time, after the console
displays the following message: 

X386  1.2E  1.0.1  /  X  Window  System
(protocol Version 11, revision 0, vendor release 5000)

the system hangs without going into the graphics mode and dump a "core.X386".
So, what am I missing?

Here is my configuration:

Hardware:
GA-486US Local Bus motherboard, 64KB Cache, CPU: Intel 486-33
8MB 60ns RAM
Quantam LPS240AT IDE Drive, 30MB for DOS
GA-200 Local Bus VGA card with 1MB memory (ET4000 based)
NEC 5FG monitor
Legend mouse in com1

Kernal: 0.1.26 (Comes with X386 binary)

Xconfig file:

RGBPath		"/usr/lib/X11/rgb"
FontPath	"/usr/lib/X11/fonts/misc/,/usr/lib/X11/fonts/Speedo/,/usr/lib/X11/fonts/75dpi/"

Keyboard
  AutoRepeat 500 5
  ServerNumLock

Mousesystems	"/dev/com1"
  BaudRate	1200

vga256
  Chipset	"et4000"
  Vendor	"legend"
  Clocks	 50 57 65 72 80 90 101 127
  Virtual	1152 900
  ViewPort      0 0
  Modes	        "1024x768" "640x480"

ModeDB
#	      clock  	horzontal timing      vertical timing
 "640x480"      50     640  672  768  850    480  550  650  650
 "1024x768"     72    1024 1032 1264 1272    768  786  791  810
 "1152x900"     80    1152 1160 1376 1416    900  900  940  948
 "1152x900"     80    1152 1184 1264 1408    900  905  908  936
                80    1152 1164 1244 1408    900  900  903  936


Thanks for your help!

Lixin
-- 
    mail:  Lixin Liu,   Department of Mathematics and Statistics,
           Simon Fraser University, Burnaby, B.C., CANADA  V5A 1S6
  e-mail:  liu@cs.sfu.ca   OR   liu@sfu.ca
   phone:  (604) 291-3422  (office),  (604) 294-6582 (home)
Xref: sparky comp.unix.bsd:4814 comp.windows.x:15814
From: hasty@netcom.com (Amancio Hasty Jr)
Newsgroups: comp.unix.bsd,comp.windows.x
Subject: Re: X386 under 386BSD does not work
Keywords: X386, 386BSD
Date: 28 Aug 92 17:55:57 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest)

In article <1992Aug27.200328.7037@cs.sfu.ca> liu@cs.sfu.ca (Lixin Liu) writes:
>Hi, everyone:
>
>After a few days of trying, I can not get X386 working on my 486 machine.
>Start with "xinit", I only got into graphics mode twice during the last a
>few days and then the system hangs. But most of time, after the console
>displays the following message: 
>
>X386  1.2E  1.0.1  /  X  Window  System
>(protocol Version 11, revision 0, vendor release 5000)
>
>the system hangs without going into the graphics mode and dump a "core.X386".
>So, what am I missing?
>
>Here is my configuration:
>
>Hardware:
>GA-486US Local Bus motherboard, 64KB Cache, CPU: Intel 486-33
>8MB 60ns RAM
>Quantam LPS240AT IDE Drive, 30MB for DOS
>GA-200 Local Bus VGA card with 1MB memory (ET4000 based)
>NEC 5FG monitor
>Legend mouse in com1
>
>Kernal: 0.1.26 (Comes with X386 binary)
>
>Xconfig file:
>
>RGBPath		"/usr/lib/X11/rgb"
>FontPath	"/usr/lib/X11/fonts/misc/,/usr/lib/X11/fonts/Speedo/,/usr/lib/X11/fonts/75dpi/"
>
>Keyboard
>  AutoRepeat 500 5
>  ServerNumLock
>
>Mousesystems	"/dev/com1"
>  BaudRate	1200
>
>vga256
>  Chipset	"et4000"
>  Vendor	"legend"
>  Clocks	 50 57 65 72 80 90 101 127
>  Virtual	1152 900
>  ViewPort      0 0
>  Modes	        "1024x768" "640x480"
>
>ModeDB
>#	      clock  	horzontal timing      vertical timing
> "640x480"      50     640  672  768  850    480  550  650  650
> "1024x768"     72    1024 1032 1264 1272    768  786  791  810
> "1152x900"     80    1152 1160 1376 1416    900  900  940  948
> "1152x900"     80    1152 1184 1264 1408    900  905  908  936
>                80    1152 1164 1244 1408    900  900  903  936
>
>
>Thanks for your help!
>
>Lixin
>-- 
>    mail:  Lixin Liu,   Department of Mathematics and Statistics,
>           Simon Fraser University, Burnaby, B.C., CANADA  V5A 1S6
>  e-mail:  liu@cs.sfu.ca   OR   liu@sfu.ca
>   phone:  (604) 291-3422  (office),  (604) 294-6582 (home)


Normally, X386 generates a stack trace dump when the kernel is not
patched for X... I know that you stated that you have the patched kernel.

Also, you are the first person reporting attempting to use X in a local 
bus and they may be a difference on a local bus implementation for the
et4000.

Could you send a stack trace dump?

Amancio Hasty
p.s. (I helped port X386 to 386bsd)
From: cflatter@nrao.edu (Chris Flatters)
Newsgroups: comp.unix.bsd
Subject: Re: 3 1/2" bootable floppy?
Date: 3 Sep 92 21:53:39 GMT
Reply-To: cflatter@nrao.edu
Organization: NRAO

In article 1667@cs.wm.edu, adrian@cs.wm.edu (Adrian T. Filipi) writes:
>	There seems to be onlly one size dist.fs file, i.e. 1.2M. Is there
>some way to turn this into a 3 1/2" or do I need to have a 1.2M floppy drive?
>I've checked the unofficial FAQ and seen nothing regarding this.

Just use rawrite.exe to write dist.fs to a 3.5" floppy.  Nothing will care
about the spare .2 Mbytes.

	Chris Flatters
	cflatter@nrao.edu
From: venkates@frith.msu.edu
Newsgroups: comp.unix.bsd
Subject: Small X for 386 bsd??
Date: 31 Aug 92 15:37:43 GMT
Organization: Michigan State University, College of Engineering, East Lansing

Hi
Even the binary only release of X for 386bsd requires lotsa disk!,
I was wondering (forgive me if this sounds stupid) if one trim the existing
X release to it's barest minimum, I am only interested in having some
sort of a windowing system running on the PC and am not paricularly
intersted in having a vast number of fonts etc being available to me.
On the same note, if X cannnot be made any smaller, are there other windowing
systems that can be used?
Thank you all in advance

Venkatesh Gopinath
Michigan state University.
Newsgroups: comp.unix.bsd
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: Re: Colorado Memory Systems tape drive
Date: Fri, 04 Sep 92 02:20:04 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Keywords: CMJ, Jumbo, DJ-20

In article <1992Sep2.134522.13938@digi.lonestar.org> mfrohman@digi.lonestar.org (Matthew Frohman) writes:
>Has anyone tried to use the DJ-20 from Colorado Memory
>Systems under 386BSD? I talked to their technical support
>and they said they have only tested the software under
>SYS V implementations of Unix. Anyone used it under BSD?

Also, you may add that they will not release any technical information
on their interface!

I have a DJ-10B, collecting dust. There is no support for QIC-40 or
QIC-80 under 386bsd, yet.

>-- 
>Matthew Frohman                                            
>UUCP:     uunet!digi!mfrohman             (214) 618-1293 (home)  
>Internet: mfrohman@digi .lonestar.org     (214) 519-3418 (work)  


Newsgroups: comp.unix.bsd
From: comrade@uniwa.uwa.edu.au (Peter Cooper)
Subject: Re: time for comp.unix.bsd.386
Organization: University of Western Australia
Date: Wed, 26 Aug 1992 11:53:41 GMT

Peter da Silva writes:

>In article <1992Aug24.074542.29794@resonex.com> michael@resonex.com (Michael Bryan) writes:
>>[I know there are a lot of strong feelings about comp.unix.bsd.386bsd
>>vs comp.os.386bsd, and other such issues.  If this is going to go
>>any further at this time, though, I'd say hold off until we get into
>>news.groups...]

>As a compromise, how about a comp.posix hierarchy for those operating
>systems that use the POSIX API as the primary programming interface?

So, will you issue the RFD for the move of comp.unix.* to comp.os.posix.* ?
;-)

I see lots of problems ahead, especially from the people who want
AT&T/USL's trademark well and truly broken.  Hmmm.  This whole BSDI
thing is getting quite tiresome.

Peter
-- 
email:  comrade@uniwa.uwa.edu.au   snail:  Peter Cooper, box 22
fax:    +61 9 380 1041                     Guild of Undergraduates
phone:  +61 9 380 3929                     University of Western Australia
"It was the banana that did it!" - Julia Marley
From: kwan@netcom.com (Kwan-Seng Low)
Newsgroups: comp.unix.bsd
Subject: Re: SCSI-2 tape and disk drives recommendations
Date: 26 Aug 92 18:16:13 GMT
Distribution: comp
Organization: Netcom - Online Communication Services  (408 241-9760 guest)

In article <JOSHUA5.92Aug25222622@csa.bu.edu> joshua5@cs.bu.edu writes:
>I'm looking for recommendations on manufacturers of SCSI disks and tape
>drives that work with an Adaptec 1542b controller.  The disk and tape
>drive will be used with BSD/386.  To date, it is my understanding that any
>devices capable of understanding most of the SCSI-2 command set will work
>best with BSD/386.  The size of the disk that I am looking for is around
>660 MB and retails for approximately $1350.  I have been cautioned against
>Figitzsu drives, don't know much about Maxtor and have had no problems with
>Seagate.   I'm looking for opinions on speed, noise and reliability.  I'm
>leaning towards a Seagate drive.  
>
>I have been told that the BSDi recommended Wangtek Archive 2150s QIC-150
>tape drive is not "current".  Refurbished ones retail for $350-$500.
>I'd prefer a new drive for roughly the same price.  
>
>All recommendations are welcome.  Feel free to post or send e-mail.
>
>				  -- Jim Peters (joshua5@cs.bu.edu)

Knowing someone from Conner, Maxtor and Seagate, and getting some honest
feedback once in a while, I would say go for Maxtor. They've the most 
experience in making 5 1/4" large capacity SCSI (>300Meg.).
	One of my housemate use to run torture test in his QA lab (i.e.
random read/write + low level format on a 7/24 basis). Never had a prob. with
Maxtor. He kill several Seagate within a week. Not all Maxtor models are good.
I would say stick with the field proven one, not the brand new model.
Generally, go for 5 1/4" disk from Maxtor, and you should be OK.
Fujitsu, might have some air-flow + heat control prob. especially on their
3.5" disk.
Seagate basically is a trash, not worth to mention.
Micropolis is a decent drive too, dunno much about it.

I've no affiliation with any of the drive manufacturer, except a satified 
customer of Maxtor.

Kwan
Newsgroups: comp.unix.bsd
From: micke@dynas.se (Mikael Hybsch)
Subject: 386BSD: Problem booting from a Seagate ST1239 (IDE)
Keywords: boot,386bsd
Organization: DynaSoft, Dynamic Software AB
Date: Wed, 2 Sep 1992 09:41:51 GMT

I have some problems trying to boot a Seagate ST1239 (200Mb 1272*9*36).
When I try to boot from the harddisk I get various read errors in
the boot code. Each time I boot it complains about the same sectors
but randomly chooses the error code.
(Different errors for the same sector each time I reboot)
The status register always has the value 59<seekdone,drq,err>.
Finally the machine resets itself.

When I boot from a floppy, I can disklabel, newfs and mount the harddisk
without any problems.

If I disklabel using fixit.fs.debug from agate:unsupported/newbootables/cgd
it boots OK, so I guess I have a workaround, but I would like to see it
boot without all the debug info.

I've used a ST3144 (130Mb) before without any problems.

(Other info: 80386-40, 8MB, Hercules, 1.44 floppy, AMI bios)

Any help is appreciated.
-- 
Mikael Hybsch, DynaSoft AB      micke@dynas.se
Liljeholmsv. 10                 Voice: +46-8-726 85 60
117 61 STOCKHOLM, SWEDEN        Fax:   +46-8-18 11 45
Newsgroups: comp.unix.bsd