HDTenEightyP/NetNews huggingface dataset:
From: berry@enuxha.eas.asu.edu (Joel R. Berry)
Subject: [386bsd]WD Patches from patchkit cause problems with bootup.
Keywords: ESDI WD 386BSD
Organization: Arizona State University
Date: Thu, 15 Oct 1992 00:01:31 GMT

BSDr's,
    I have installed the patch kit  ( beta ) and all works well except
when I add the on that tells the wd driver to return errors when it
finds one on the disk.  My disk is an Micropolis 330M esdi drive.  The
problem happens upon running fsck.  It fails when checking.  The blocks
that were bad are placed into the bad144 table, but I guess that fsck
is not reading that or something.  How should I go about having 
fsck know about my errors but not dying from them.  Fsck stops with
a read error on the bad spots.  What should I do about it.  For now
I have just removed that patch and have gone on from there, but I would
like to be able to install it for completion reasons.  
	Sorry if this is a repost, but I did not receive any replies from
the previous post so I think that it did not make it off campus.  Also,
our news reader has been doing some wierd things, so please respond
via mail if possible.  Thanks for any info.
 joel berry
--

-----------------------------------------------------------
Joel Berry | berry@enuxha.eas.asu.edu
-----------------------------------------------------------
Newsgroups: comp.unix.bsd
From: rich@Rice.edu (Richard Murphey)
Subject: Re: kermit for 386BSD
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
	<1992Oct14.021724.7758@burns.jpl.nasa.gov>
Date: Wed, 14 Oct 1992 04:42:50 GMT

In article <1992Oct14.021724.7758@burns.jpl.nasa.gov> hand@spc9.jpl.nasa.gov (Kolin Hand) writes:
   In article <92287.113452CALT@SLACVM.SLAC.STANFORD.EDU> <CALT@SLACVM.SLAC.STANFORD.EDU> writes:
   >I am looking for Kermit for 386BSD. Any suggestions?
   >Thanks!
   >
   >Ching Shih
   >shih@cithex.caltech.edu

   The latest version of Kermit, available from watsun.cc.columbia.edu, 183
   I believe, ports with very little effort.  Look for cku183.tar.Z on that site.

or /usr/src/othersrc/public/kermit-5a in the 396BSD etc01 distribution.  Rich

   Kolin

   +===========================================================================+
   +  "Guilt Trip:  The nuclear weapon of relationships."  -- K. Hand          +
   +---------------------------------------------------------------------------+
   +  Kolin E. Hand                              hand@spc7.jpl.nasa.gov        +
Newsgroups: comp.unix.bsd
From: paoletti@cps.msu.edu (David R. Paoletti)
Newsgroups: comp.unix.bsd
Subject: neg free space on 1023 cyl?
Date: 10 Oct 92 01:08:30 GMT
Organization: Dept. of Computer Science, Michigan State University
Originator: paoletti@pacific.cps.msu.edu

I am trying to reinstall 386BSD on my new machine, which
includes a Fujitsu 2266 SCSI drive.  The AHA-1542B translates
it to 1023 cyl, 64 heads, 32 sectors/track.

When I try to run the install program, it reports that my
drive has -327MB free!  Does this sound like a wrap-around
problem?  Is it that I must use disklabel on this drive?

I tried doing a 'disklabel -r as0' and it did not fill in
any values for fields such as the cylinders, etc.  Does
this only work after you've disklabel'ed the drive?

Anyone have a working disktab entry for this drive?

Thanks!
  Dave Paoletti :)
Newsgroups: comp.unix.bsd,alt.sources
From: julian@tfs.com (Julian Elischer)
Subject: Re: The ultimate 386BSD machine?	(FAQ fodder)
Keywords: 386BSD
Organization: TRW Financial Systems
Date: Fri, 9 Oct 1992 16:57:58 GMT

In article <1992Oct8.164919.14096@eab.retix.com> erik@eab.retix.com (Erik Forsberg) writes:
>In article <Bvsss4.9nz@ibmpcug.co.uk> adrian@ibmpcug.co.uk (Superuser) writes:
>>In article <1992Oct8.072512.8700@elroy.jpl.nasa.gov> earle@elroy.jpl.nasa.gov (Greg Earle - Gainfully Unemployed) writes:
>>>  As an adjunct to this, I expect Julian to jump in with "But an Adaptec 1742A
>>>  is supported with my new SCSI subsystem ... ".  Fine, but can one get the
>>>  system up first (with it installed) to get to the point where one can
>>>  recompile the kernel with the new SCSI subsystem?
>>>
>>
>>Julians SCSI system works by setting th 1742B into 1542 mode, and then
>>when the probe works out its a 1742, it shoves the card into enhanced
>>mode itself.
>>
>
>This seems to be a BAD approach. It would EXCLUDE all existing 1740 cards
>from functioning. ONLY the newer 1740A (and obviously 1742A) allows switching
>between standard and enhanced mode at runtime. The older 1740 (which probably
>still is the most common Adaptec EISA card out there) requires you to
>download firmware that is specific to the operating mode.
>
>So, useful support for Adaptec 1740 cards, requires support for enhanced
>mode in everything (boot blocks, standalone boots and kernels).

I do not set the 1740 to standard mode and then move it to enhanced
mode. When I get the board, I set it into enhanced
mode. However I make no assumptions
about what mode it is already in.
Obviously if you wanted to run it in standard mode then you would use the 1542
driver instead. (However I wouldn't recommend it as the 1542 emulation 
ona 1740 has BUGS)

Theoretically the new boot blocks should support the 1740 in extended mode
(but at present seem to only be able to boot
a partition starting at the beginning of the disk..(I'm working on it))
>
>-- 
>---------------------------------------------------------------------------
>Erik Forsberg, erik@eab.retix.com Phone: (310) 476-7133 FAX: (310) 476-7657

+----------------------------------+       ______ _  __
|   __--_|\  Julian Elischer       |       \     U \/ / On assignment
|  /       \ julian@tfs.com        +------>x   USA    \ in a very strange
| (   OZ    ) 2118 Milvia st. Berkeley CA. \___   ___ | country !
+- X_.---._/  USA+(510) 704-3137(wk)           \_/   \\            
          v



Newsgroups: comp.unix.bsd
From: gl5007@ehsn5.cen.uiuc.edu (Gil Ephraim Levendel)
Subject: [386BSD] Communication Program
Organization: University of Illinois at Urbana
Date: Sun, 11 Oct 1992 01:05:15 GMT

Hi,

I am looking for a communications program to use with
386bsd. I have heard of one named Pcomm, but I do not
know where I can ftp it.

Does anyone know where can I find this or any other
communications program?

Thanks,
Gil
From: james@sol1.east-london.ac.uk (Gabby Cheema told me to do it)
Newsgroups: comp.unix.bsd
Subject: slip and internal modems under bsd386
Date: 15 Oct 1992 09:07:13 -0500
Organization: UTexas Mail-to-News Gateway
NNTP-Posting-Host: cs.utexas.edu



In the pd bsd386 does slip work?  Any know problems with it?
Are multiple internal modems supported?


I' like to use a pc as a slip server- comments please.

james@sol1.pel.ac.uk
Newsgroups: comp.unix.bsd
From: klarenbe@chx400.switch.ch (Paul Klarenberg)
Subject: Solution to vectra hang problem.
Summary: Solution to vectra hang problem.
Keywords: HP, Vectra, boot, hang, copyright
Organization: Swiss Academic and Research Network SWITCH
Date: Fri, 16 Oct 1992 11:07:20 GMT

[I'm posting this for a friend]

The solution to the Vectra 386/20N hang after copyright.

  I tracked it down to a problem in pcprobe, the probe routine
for the console. As Terry Lambert pointed out in his reply to
my first posting a fix for the 'hang after copyright' is in the beta
testkit. As I only have the alfa-3 version (2-sep 92) I do not know
exactly what the fix in the beta-kit is..
  But placing a DELAY(1000) inbetween outb(KBOUTP, CMDBYTE); and
kbd_CMD(KBC_RESET); in pcprobe (file ..../isa/pccons.c) solves the
problem. Ok but now the *why*!
  I looked in the Bios Technical Reference Manual for the Vectra 386/20N,
but nothing is said about the time the keyboardcontroller (8042 micro
controller) takes to execute a command. The 8042 is a single chip
microcontroller that executes a program stored in an embedded ROM (16K).
The program controls the keyboard and several settings of the main board
(password, fast reset for mode switching etc..) On a 386/20N it also
controls the built in bus mouse.
   The routines kbc_8042cmd() and kbd_cmd() in pccons.c only test if the
command has been removed from the inputregister of the controller. They do
not test that the command finished executing inside the controller. So I
think the problem is that the keyboard controller locks up because two
commands are given too soon after each other.

Reinier Kleipool
Reinier.Kleipoo@HPITCB.hp.hp.400net.nl
Reinier Kleipool /HPITCB/85
From: terry@cs.weber.edu (A Wizard of Earth C)
Newsgroups: comp.unix.bsd
Subject: Re: Memory problem
Keywords: memory
Date: 16 Oct 92 19:56:26 GMT
Organization: Weber State University  (Ogden, UT)

In article <1bmcvjINN5m3@corax.udac.uu.se> goran@astro.uu.se (Goran Hammarback) writes:
>It's a known problem that 386BSD just hangs if you fill the swap.
>I call it a bug (I doubt you will find anyone saying it's feature 8-) ).

Uhhh... it encourages tight coding and the development of shared libraries?

8-). 8-).


					Terry Lambert
					terry@icarus.weber.edu
					terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------
From: CALT@SLACVM.SLAC.STANFORD.EDU
Newsgroups: comp.unix.bsd
Subject: clock.exe
Date: 9 Oct 92 17:16:52 GMT
Organization: Stanford Linear Accelerator Center

Could someone out there tell me where to get the clock.exe program?
Thanks!

Ching Shih
shih@cithex.caltech.edu
Newsgroups: comp.unix.bsd
From: gottloeb@eel.dsd.trw.com (Jeffrey R. Gottloeb)
Subject: Re: fax software for 386bsd?
Organization: TRW, INC.
Date: Wed, 14 Oct 1992 22:04:15 GMT

In article <1992Oct14.184210.16229@gumby.dsd.trw.com> gottloeb@eel.dsd.trw.com (Jeffrey R. Gottloeb) writes:
>In article <1992Oct5.105838.13230@Informatik.TU-Muenchen.DE> gebhart@Informatik.TU-Muenchen.DE (Ralf Gebhart) writes:
>>In article <1992Oct5.103838.13036@Informatik.TU-Muenchen.DE> gebhart@Informatik.TU-Muenchen.DE (Ralf Gebhart) writes:
>>>>
>>>Hi
>>>I'm currently working on porting GNU-netfax to 386BSD.
>>>I have already compilid it (need GNU-make for this).
>>>With the exception of one ioctl, I only had to change some #defines.
>>>I don't know yet if that ioctl is really necessary, because I don't know
>>>what it does. Ultrix and SUNos have it, but 386BSD not. Unfortunately
>>>I couldn't get any docs/info about that ioctl yet.
>>>Another problem is, I am currently very busy with other things,
>>>so it will take at least another month, til I have finished that beast.
>>>BTW: I'm working with a ZyXEL 1496E.
>>>
>>
>>I forgot some things to mention.
>>I used Version 3.2.1 of GNU-fax
>>
>>and is there anyone who can tell me what 
>>
>>ioctl(fd, TCXONC, TCOOFF);  exactly does ?
>>
>>I know it has something to do with XON/XOFF, but is so special to it,
>>can it be replaced by one of the usual XON/XOFF-related ioctl ?
>>
>>
>>      Snake
>>
>
>
>I've got most of done and am testing it right now.  I am able to send faxes
>out via the spooler but I am having difficulty receiving faxes.  The problem
>seems to be a time-out problem after receiving the CONNECT message.
>
>One thing I found out about the ZyXEL's is that they are not returning
>Class 2 values that are strings (eg. FCSI, FTSI) properly.  The values
>should have double-quotes around them (eg. +FCSI:"18005551212") but do not
>(at least with the V5.02 ROMSs).
>
>I also needed to increase the timeout value TIMEOUT_ANSWER in c2proto.h from
>15 seconds to 60 seconds to allow for long carrier detect times (all those
>protocols :-).
>
>Something that made by efforts easier was a patchfile that was posted here
>earlier.  If you don't have it, email me.

Actually it was comp.dcom.modems.  My mistake.

>
>I don't remember at the moment what I changed that ioctl to but I can check
>tonight.
>
>Jeff Gottloeb
>gottloeb@gumby.dsd.trw.com
From: pbd@runyon.cim.cdc.com (Paul Dokas)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] vmstat: version for ISA architecture out?
Keywords: memory, vmstat
Date: 16 Oct 92 14:30:56 GMT
Organization: ICEM Systems, Inc.

In article <1bm3ntINNbe4@frigate.doc.ic.ac.uk>, kd@doc.ic.ac.uk (Kostis Dryllerakis) writes:
|>                                  The copy available from the BSD reno has to be modified
|> and I am not the expert to do so. Not much has to be done though; if anybody has done so
|> I would be obliged for a copy of the modified source!

I too tried to get the reno version of vmstat to work on 386BSD, but unfortuately I couldn't
figure out how to make it work.  The place the I couldn't figure out is with names.c.  It
requires several kernel symbols names that I just couldn't find in 386BSD.  The offending
symbols were _hp_dinit for hp300, _mbdinit and _ubdinit for vax, etc.

I looked through /sys on a SUN and found the files with similar names in them, but I couldn't
find similar definitions in 386BSD.

My guess is that these symbols are part of the ATT (boo hiss) code that was replaced during
the Great Code Purge(tm).

Anyone have suggestions?
-- 
#include <std.disclaimer>
#define FULL_NAME                          "Paul Dokas"
#define EMAIL                              "pbd@runyon.cim.cdc.com"
/* we are realizing infinite possibilities in exchange for our soul */
Newsgroups: comp.unix.bsd
From: stark@cs.sunysb.edu (Gene Stark)
Subject: Re: Can't make Logitech mouse working right
Organization: SUNY at Stony Brook Computer Science Dept.
Date: Mon, 12 Oct 1992 14:42:24 GMT

I have a Logitech mouse, model number MB-82-9F.
I had similar problems to what you describe.
I got it to work by putting the following in my XConfig:

	Microsoft "/dev/com1"
	Emulate3Buttons

Comment out the BaudRate and SampleRate stuff, they seem to screw it up.

							- Gene Stark
From: bs@Germany.EU.net (Bernard Steiner)
Newsgroups: comp.unix.bsd
Subject: Re: kernel too large to load
Date: 16 Oct 1992 11:54:08 GMT
Organization: EUnet Backbone, Dortmund, Germany
Distribution: comp
NNTP-Posting-Host: walhalla.germany.eu.net

In article <1992Oct16.043837.3822@tfs.com>, julian@tfs.com (Julian Elischer) writes:
= >2)	Link it to load above 1 Meg and use Julian's boot blocks to load it;
= >	you may not be able to use the memory below 1 Meg unless you write
= >	more code to add it to the usable pool.
= 
= the loader does this just fine, but the kernel explodes.
= Bill tells me you need som patches to load above 1MB.
= I'll ask him this weekend.

Where is /boot, anyway ?!
I mean, it's OK putting the bootstrap outside the filesystem, but then
the normal /boot tends to ask about the kernel name, boot flags and other
nifty little things.

Just a thought
-Bernard
-- 
Bernard Steiner, FB Informatik/IRB, Uni Dortmund,    vox +49 231 755 2444
Postfach 500500, D-W-4600 Dortmund 50, Germany       fax +49 231 755 2386
bs@Germany.EU.net          ...!uunet!unido!bs

*III  And they gave it Instructions, but knew it not. } From The Book of Nome,
*IV   It is, they said, a Box with a Funny Voice.     }      Mezzanine v.III-IV
Newsgroups: comp.unix.bsd
From: pjh@mccc.edu (P. J. Holsberg)
Subject: 386BSD + MS-DOS
Organization: The College on the Other Side of U. S. 1
Date: Sun, 11 Oct 1992 00:29:54 GMT

I have access to a lab full of 386 PCs running MS-DOS and a Novell
network. Would it be feasible to partition their HDs and install 386BSD?
Would that require reformatting and re-installing all the MS-DOS
software? Would 386BSD's networking work over Novell network hardware?

Thanks,
Pete

Newsgroups: comp.unix.bsd
From: toreh@bootes.sds.no (Tore Haraldsen)
Subject: Re: 386BSD and DOS partitioning help.
Organization: Statens Datasentral A/S, SDS, Norway
Date: Fri, 9 Oct 1992 00:25:23 GMT

What I have been doing, is to use the standard install procedure to get
the 386bsd partion created. Then I run the fixit disk and change the
disklabel partitioning to suit me. Then I maually move the stuff from
the dist.fs disk onto the disk.

Of course, it helps gretly if you got a second disk. In that case, use
the fixit disk to move the original installation to the second disk, and
then rdconfigiure the first.

The easiest way to get a second disk up, is to swith unit numbers and do
a pseudo-install on it...

I think, if you need detailed info, that Terry's got a very good
step-by-step description...


-- tore
Newsgroups: comp.unix.bsd
From: robert@psych (Robert Dal Santo)
Subject: [386BSD] SCSI Driver for Seagate ST01
Organization: Psychology Department, University of Queensland
Date: Thu, 15 Oct 1992 03:17:23 GMT



        Has anyone produced a working driver for the seagate 
ST01 SCSI card. Or is anyone working on one. This enquiry
is for someone who wants to do a port but would prefer not
to if its already been done.

Thanks,

===========================================================================
Robert Dal Santo               Phone +61 7 365 6687
                               Fax   +61 7 365 4466
Department of Psychology,      
University of Queensland 4072,
AUSTRALIA.                     

"I've reached the driveway to destruction and I'm taking the stationwagon."
===========================================================================
From: dean@ksr.com (Dean Anderson)
Newsgroups: comp.unix.bsd
Subject: Re: HELP: wiped out my DOS partition
Date: 12 Oct 92 19:28:01 EDT
Organization: Kendall Square Research

>  ha ha ha ha ha ha..  You did the same thing I did!!!
>
>   The "d" partition cann't be used as a partition ..  the 'd'
>partition is the whole drive..  So even though you set it aside as 70meg
>for unix. It actually was the first 70meg of your HD.  Which is probably
>where you dos is..

This shouldn't happen.  The driver should look at the disk label and the
partition table to determine the drive geometry.  A bit of effort has gone
into developing a common interface (the disklabel, /etc/disktab, and 
disklabel & diskpart commands) to avoid just these pitfalls.

This just demonstrates that the device driver writer is really in control
of the operating system. ;-)

I am particularly disappointed with the changes to ufs_disksubr.c for 
dos partitions.  This is supposed to be a machine independent file
for use by drivers. (someone correct me if I am wrong)

The PC BSD's should look at the dos partition table and create multiple
logical disk drives, one for each partition.

This has the following benefits:

1. Doesn't change machine independent code.  This makes it easier to
integrate future changes to BSD code, and contribute changes back to
Berkeley.

2. Makes it possible to mount Dos "drives".  A dos vfs is needed.

3. Makes it possible to ignore that dos exists and use the whole drive
without a dos partition table.  This is particularly attractive is you
have a large disk,  because dos will not work happilly with disks of
greater than 1024 cylinders without a lot of egregious hacking which
ultimately hurts ufs performance.

		--Dean
--
Dean Anderson			dean@ksr.com  |  I'm not voting because the
KSR Computing Facilities                      |  lack of a candidate has
Kendall Square Research                       |  co-opted me out of the process
From: rich@Rice.edu (Richard Murphey)
Newsgroups: comp.unix.bsd
Subject: Re: [XFree86] how do i use xmkmf?
Date: 14 Oct 92 18:13:33 GMT
Article-I.D.: kappa.RICH.92Oct14121333
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University

In article <1992Oct14.090956.1@max.u.washington.edu> anything@max.u.washington.edu writes:
   Can anyone tell me in a few easy sentences how to use xmkmf? it has me totally
   baffled, keeps giving me error messages about commands not existing, etc..

Use 'xmkmf -a' to create the Makefile form the Imakefile and run make
depend, etc.  It's all in 'man xmkmf'.  Rich
From: eb@felix.Sublink.Org (Enrico Badella)
Newsgroups: comp.unix.bsd
Subject: Re: Help on Xt library and Motif ...
Date: 15 Oct 92 18:20:23 GMT
Organization: Soft*Star s.r.l, Torino, Italy

In article <1avr4oINN4m2@agate.berkeley.edu> randyc@soda.berkeley.edu (Yen-Pang Randy Chou) writes:
>A few weeks ago someone mentioned that there was a bug in gcc and that
>the Xt library had to be patched in order to successfully compile Motif.  
>Does the new release of XFree86 fix the problem?  If not, where can I get
>a working Xt library?  Also, what problems does the old Xt library produce?

You can use the gcc that comes with 386BSD-0.1 to compile ALL X11R5-pl.17
and OSF/Motif 1.1.x
I have done it with absolutely no problems.
I also compiled mxgdb (frontend to gdb) and xgen both of which use
X11R5 and Motif.

-- 
Enrico Badella				Internet: eb@felix.sublink.org
Soft*Star s.r.l.			          eb@icnucevx.cnuce.cnr.it
Via Camburzano 9			Phone:    +39-11-746092
10143 Torino, ITALY			Fax:      +39-11-746487
Newsgroups: comp.unix.bsd
From: m.dickson@csi.compuserve.com (Michael C. Dickson)
Subject: Re: 386BSD won't boot with AMI BIOS/Gateway 2000
Keywords: AMI Gateway 2000
Organization: Systems/Monitor Group, CompuServe Incorporated.
Date: Thu, 15 Oct 1992 16:37:16 GMT

In article <1992Oct14.225619.26784@ccu.umanitoba.ca> rahardj@ccu.umanitoba.ca (Budi Rahardjo) writes:
>Newsgroups: comp.unix.bsd
>Path: ihz.compuserve.com!uunet!charon.amdahl.com!pacbell.com!ames!haven.umd.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!destroyer!cs.ubc.ca!unixg.ubc.ca!kakwa.ucs.ualberta.ca!access.usask.ca!ccu.umanitoba.ca!rahardj
>From: rahardj@ccu.umanitoba.ca (Budi Rahardjo)
>Subject: Re: 386BSD won't boot with AMI BIOS/Gateway 2000
>Message-ID: <1992Oct14.225619.26784@ccu.umanitoba.ca>
>Keywords: AMI Gateway 2000
>Sender: news@ccu.umanitoba.ca
>Nntp-Posting-Host: antares.cc.umanitoba.ca
>Organization: University of Manitoba, Winnipeg, Canada
>References: <1992Oct13.034643.15109@unvax.union.edu>
>Date: Wed, 14 Oct 1992 22:56:19 GMT
>Lines: 17
>boehme@unvax.union.edu (Eric M. Boehm) writes:
>
>>I have seen oblique references to a problem with AMI BIOS in other
>>messages. I recently upgraded my BIOS from 030389 to 050591. 386BSD
>>still won't boot. The drive light comes on and stays on. Ctrl-Alt-Del
>>won't regain control -- time for the red button.
>
>I haven't seen (heard) anybody can get 386bsd up and running on a
>Gateway machine. I have posted twice, but the only responses I have
>were me too mails.
>I phoned Gateway tech. rep. and he knows nothing of 386BSD.
>I guess we (gateway owner) are stuck. I guess I should stick with Linux then.
>
>-- budi
>-- 
>Budi Rahardjo <rahardj@ccu.umanitoba.ca>
>Unix Support - Computer Services - University of Manitoba

  I've had 386BSD running on several gateway 2000 machines.  I did have some 
trouble with the ATI Ultra card (no boot) but when that was swapped out for 
a plain vanilla vga card everything came up fine.  Perhaps the video card is 
your problem?

Mike
Newsgroups: comp.unix.bsd
From: zawada@softage.demon.co.uk.demon.co.uk (Mark D Simpson)
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Newsgroups: comp.unix.bsd
Subject: Re: clock.exe
Date: 12 Oct 92 08:15:52 GMT
Organization: Uni-Duisburg FB9 Datenverarbeitung
Reply-To: veit@du9ds3.uni-duisburg.de
NNTP-Posting-Host: du9ds3.uni-duisburg.de

In <92283.091652CALT@SLACVM.SLAC.STANFORD.EDU> CALT@SLACVM.SLAC.STANFORD.EDU writes:

>Could someone out there tell me where to get the clock.exe program?
>Thanks!

>Ching Shih
>shih@cithex.caltech.edu

Don't get it. It is obsolete. The XFree86 X server has its own, better working
clock detection code. The clock.exe program worked only with VGA and
Tseng SVGA's.

Better try 

X386 >& x386.log

to find out about the clocks of your board.


Holger
-- 
|  |   / Dr. Holger Veit         | INTERNET: veit@du9ds3.uni-duisburg.de
|__|  /  University of Duisburg  | "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
|  | /   Dept. of Electr. Eng.   |   Sorry, the above really good fortune has
|  |/    Inst. f. Dataprocessing |      been CENSORED because of obscenity"