HDTenEightyP/NetNews huggingface dataset:
From: rlcarr@animato.network23.com (Rich Carreiro)
Newsgroups: comp.os.minix
Subject: some Amiga MINIX questions
Distribution: world
X-NewsSoftware: GRn 1.16e (7/4/92) by Mike Schwartz & Michael B. Smith
Date: 29 Sep 92 19:23:27 EDT
Organization: The Other Side of Life

Hello!
 I have Amiga MINIX 1.5, and have updated it to 1.5.10.2 and
have a few questions.  First, my configuration...
A2000+A2630 accelerator, 9 meg RAM, A2091 SCSI controller.
Now, I have two partitions for MINIX.  I have a 800K partition that
initialize my root filesystem (RFS) from, and a 15M partition that
has everything else.

As it currently stands, when I boot MINIX, it asks for the RFS.  I give
it "3,3" (since the 800K partition is paritition 3) and it loads the 
contents of that partition into a 800K RAM disk and give me the login
prompt.

What I *want* to do is use the ACTUAL RFS partition as the RFS, instead
of using a RAM image of it.  However, I still want to have, oh, about
a 512K RAM disk around (initially empty) as well.

So, what do I have to do to accomplish this?

Also, is there anywhere I can get a C compiler for MINIX that
(a) has floating point support, either by supporting my 68882 (preferred)
    or by software floating point math?
(b) is 32-bit instead of 16-bit, or is this bad because MINIX itself is
    only 16 bit?

Thanks for any answers!

-- 
Rich Carreiro                                  Home: (401)841-8514
rlcarr@animato.network23.com
uunet.uu.net!animato!rlcarr
From: frain@cis.ksu.edu (Jerry Frain)
Newsgroups: comp.os.minix
Subject: Gcc and Emacs for 68k (was Re: MacMinix and System 7)
Date: 27 Sep 92 20:47:41 GMT
Organization: Kansas State University
NNTP-Posting-Host: depot.cis.ksu.edu

frain@cis.ksu.edu (Jerry Frain) writes:

> I just got MacMinix 1.5, and I am wondering if anyone has it running
> well under System 7.  I've got an SE/30, 4MB RAM, System 7.  I've had
> to run 6.0.8 to get Minix to run on it.  I've tried ditching my inits,
> virtual memory, Mode32, etc, but nothing seems to help.

I've already received several replies regarding where to get the
patches (plains.nodak.edu:pub/Minix/ftp_contrib/mcminix).  Thanks to
all who responded.

Now I am curious about where to get the 32-bit gcc for m68k, and emacs
for the same.  The Minix Information Sheet shows them to be at plains
in the pub/Minix/uk directory, but the only thing there is the `Index'
file, and a `mincen' directory which evently leads to TeX binaries.

Does anyone know where I can find these items?

Mucho thanks in advance,

  --Jerry Frain, frain@cis.ksu.edu
Newsgroups: comp.os.minix
From: englhp@rosie.uh.edu (Lester, Samuel H.)
Subject: gcc standard lib includes and g++libc.a (m68k)
News-Software: VAX/VMS VNEWS 1.41    
Organization: University of Houston
Date: Tue, 29 Sep 1992 15:27:00 GMT

	I have been using gcc 2.2.2 and assorted utilities from
ftp.thp.uni-koeln (many thanks to Rainer Orthhael, Michael Haardt,
Wolfgang Denk, and others involved in porting and posting to
this archive).  I would like to find the full ANSI includes
to gcc 2.2.2 and any other relevant docs without having to
download all the source from prep.ai.mit.edu (the source alone
is 6+ megs compressed, and I have very little disk space left);
it seems like this would be an appropriate post to the archive?
	Also, if anyone has the g++libc.a for Minix 68k, could
they send, post, or diff it?  I have been trying to compile it 
from source, but I have not found the right memory settings
(not to mention the ANSI includes), and it seems it may take
more than the appx. 7 megs I have free.
	Finally, if there is a mailing list for the gcc project,
I would be interested in getting on it, and perhaps contributing
once I get a few of these details worked out.
	Thanks,
			Samuel

Newsgroups: comp.os.minix
From: al@escom.com (Al Donaldson)
Subject: Re: (none given) was Re: Signal handling
Reply-To: al@escom.COM (Al Donaldson)
Organization: ESCOM Corp., Oakton VA (USA)
Date: Sun, 27 Sep 1992 03:26:41 GMT

Yesterday I wrote:
>after the first login, successive calls to dev_open() were made with
>an inode reference count (rip->i_count) of 3...

Well, if any of you have been playing along at home, you're probably
wondering what I've been smoking..

The reason I had this problem was that I have a daemon process running
in the background that had the console opened for stdout and stderr.
Hence, there are two additional file descriptors and rip->i_count is 3
instead of 1.  The reason that I didn't see this during the first login
was purely a matter of timing -- when init fork'ed a new process that
would eventually become the daemon, the parent managed to get back and
start the first login before the child could exec the daemon.  However,
when startup() kicked off successive logins, the daemon was running
and login couldn't get a control terminal.

I'd like to say that I fully understand that once I start adding
non-standard things like daemons to MINIX I'm off in uncharted
territory and am likely to run into all sorts of unexpected stuff
(lions and tigers and bears, oh my).  However, now that I have found
this, I'm at a loss of what to do.  I've considered the following:

 1-Increase the check for rip->i_count from 1 to 3 in fs/device.c.

	  if (rip->i_count > 3) return(OK);

   As I mentioned yesterday, this *seems* to work without any problems.
   But it seems ugly to have to hack FS every time I add another daemon.
   I guess I don't really see the reason for the check, perhaps to
   avoid unnecessary file activity..  Maybe this whole statement
   could be removed.

 2-I guess I could change the daemon to open stderr whenever it
   needs to write a message to the console instead of just opening
   it once and leaving it open.  But this raises the possibility,
   however slight, that the daemon will have the console opened
   when init kicks off a new login, and we're back where we started.

 3-I could just put the daemon code back inside init, where it
   probably belongs.  This way, when I opened the console for an
   error message I could be sure I was not starting a login on
   the console.  Life would be a lot simpler.

 4-It seems to me that FS should be modified to ignore any use
   of a device by processes outside the process group.  For example,
   the daemon is in another process group so its file descriptors
   should be ignored.  I haven't really thought through what would
   happen in a real multi-user system; maybe this opens up all
   sort of holes.  I don't know.

Although this doesn't really pertain to the MINIX mainstream, I sure
would appreciate any thoughts that you readers might have.  It seems
that sooner or later someone else will run into this same problem.

I'd also like to apologize for being frustrated by the lack of
response from the net when I first raised my question about problems
with signals.  Now I understand why--no one else had problems..
It also shows that I should have checked my own code first.

Al
From: dcope@vtrm01.uucp
Newsgroups: comp.os.minix
Subject: Re: Minix and PPP?
Date: 1 Oct 92 13:27:22 EST
Organization: Vickers, Inc. - Troy, MI, USA

In article <1992Sep30.093545.1@eis.dofasco.ca>, fraser_h@eis.dofasco.ca writes:
> In article <1992Sep27.194244.13929@terminator.cc.umich.edu>, pauls@css.itd.umich.edu (Paul Southworth) writes:
>> Has anyone successfully used PPP with Minix?
>> 
>> 
>> Paul Southworth                    |     ftp redspread.css.itd.umich.edu
>> Consulting and Support Services    |        Anonymous Political Archives
>> Information Technology Division    |                     100% 386BSD 0.1
>> University of Michigan, Ann Arbor  |  Coming soon: mirror of ftp.eff.org
>> 
>>   <Representing myself.  Everything I say is for educational use only.>
> 
> Along the same lines, has KA9Q been successfully ported to Minix?
> 
Yes,  on 386 minix of course

Don	(vtrm01!dcope@vela.acs.oakland.edu)

> -- 
> Hugh Fraser					Dofasco Inc.
> (fraser_h@eis.dofasco.ca)			1330 Burlington St East
> (416)544-3761 X6941				Hamilton, Ont. L8N 3J5 Canada
Newsgroups: comp.os.xinu
From: bri@pegasus.mit.edu (Brian D. Carlstrom)
Newsgroups: comp.os.xinu
Subject: Re: xinu question #2
Date: 29 Sep 92 01:52:02 GMT
Organization: mit

In article <1992Sep28.235857.29953@u.washington.edu> mpark@u.washington.edu writes:
>   When XINU runs on a 68000 machine, does each process
>   need its own supervisor stack in addition to its
>   user stack, or can all processes share one supervisor stack?
>Does anybody out there have any experience with XINU & 68000?

i was wondering speicifically if anyone has an implementation
of XINU running on m68k apollos?

-bri
Newsgroups: comp.os.xinu
From: Robert C LaLonde <rlalonde@magnus.acs.ohio-state.edu>
Subject: PC XINU
Organization: The Ohio State University
Date: Mon, 28 Sep 1992 23:08:41 GMT
X-Mailer: ELM [version 2.3 PL11]

I am taking a computer science course in XINU.  We only have a few SUN 3 
machines with XINU.  I have heard about a PC version of XINU that can work
on a PC 8088.  If I could get my hands on this, preferably for no or little 
money as I am a student and haven't even used xinu enough to know if I could
like to use it for real.  I don't need the virtual memory ability.

	Any info. will be helpfull.

	Thank you,

	-Rob

-- 
Robert C. LaLonde (Rob)           |Internet: lalonde.6@osu.edu,
                                  |        : lalonde@cis.ohio-state.edu,
Computer Science Undergrad        |        : rlalonde@magnus.acs.ohio-state.edu
Senior Year                       | or UUCP: osu-cis!lalonde
Secretary of The Ohio State University Student Chapter of ACM.
Newsgroups: comp.os.xinu
From: laverman@cs.rug.nl (Bert Laverman)
Subject: Re: LSI 11 cross-compiler support
Originator: laverman@rug17
Organization: Dept. of Computing Science, Groningen University
Date: Mon, 5 Oct 1992 08:09:35 GMT


Reading this gcc-related posting, I cannot help but come up
with a related question. Is this the only freely available
pdp/lsi-11 C compiler? Or even: is this the only freely
available compiler for whatever language?
  I'm currenlty trying to get small-c to compile under unix
(it's made to compile with itself, and that includes a lot
of magic with pointers...) so i can have a go at letting it
generate pdp/lsi-11 code.

Greetings, Bert
-- 
#include <std/disclaimer>

  Bert Laverman,  Dept. of Computing Science, Groningen University
  Friendly mail to: laverman@cs.rug.nl      The rest to: /dev/null
From: mpark@milton.u.washington.edu (Michael Park)
Newsgroups: comp.os.xinu
Subject: xinu question #2
Date: 28 Sep 92 23:58:57 GMT
Reply-To: mpark@u.washington.edu
Organization: University of Washington, Seattle

Well, last time I asked a question things worked out so well
that I've decided to do it again; today's question is:

   When XINU runs on a 68000 machine, does each process
   need its own supervisor stack in addition to its
   user stack, or can all processes share one supervisor stack?

Does anybody out there have any experience with XINU & 68000?

-- 
Ciao-abunga!           +-------------------------------------+
Michael Park           | This space intentionally left blank |
mpark@u.washington.edu +-------------------------------------+
From: droms@SOL.CS.BUCKNELL.EDU (Ralph E. Droms)
Newsgroups: comp.os.xinu
Subject: LSI 11 cross-compiler support
Date: 1 Oct 92 10:42:23 GMT
Reply-To: droms@bucknell.edu
Organization: The Internet

Turns out there's a set of patches for gcc that can build a
cross-compiler targeted at the PDP 11 instruction set.  The output
seems mostly compatible with the UNIX format for PDP 11 assembler
language.  I've built the cross-compiler, and it seems to work OK.

The problem is that the cross-compiler, as distributed, uses the
entire PDP 11 instruction set.  I have zero experience with gcc; is
there anyone else interested in working with me to retarget the
cross-compiler at the LSI 11 instruction set?

- Ralph Droms                 Computer Science Department
  droms@bucknell.edu          323 Dana Engineering
  (717) 524-1145              Bucknell University
  (717) 524-3760 (fax)        Lewisburg, PA 17837
Newsgroups: comp.os.xinu
From: jld@datascope.com (Jay L. Davis)
Subject: Availability of Xinu/tcpip distribution
Organization: Datascope Corp.
Date: Mon, 28 Sep 1992 21:28:48 GMT

Other than ordering the distribution from Prentice Hall, is the XINU/TCP-IP
distribution available on-line?

Thanks, Rowl
From: sdo@CS.PURDUE.EDU (Shawn Ostermann)
Newsgroups: comp.os.xinu
Subject: Re: ctxsw routine for M68000
Date: 6 Oct 92 20:21:34 GMT
Distribution: world
Organization: The Internet


>>>>> On 6 Oct 92 07:48:25 GMT, ogicse!news.u.washington.edu!stein.u.washington.edu!mpark@decwrl.dec.com  (Michael Park) said:

	Michael> 2. Given (1) above, two questions spring to mind:
	Michael> a. since the USP is never saved, does that mean that
	Michael>       the 68000 is ALWAYS in supervisor mode?  Or,

This is correct.  Non-VM versions of Xinu all run in "priveleged"
state, whatever that is for a particular machine.  Xinu was designed
to be a very small, fast system; protection was not a high priority.
Switching from user to protected mode is very expensive, particularly
so on modern RISC machines, because it generally involves a system
trap, saving all the registers, and etc, and it needs to happen on
every system call.  Even on a big CISC chip like the 68020, it's still
quite expensive.


	Michael> 3. I was leafing through the Mac edition of the xinu
	Michael>    book, and was forced to conclude that Mac xinu
	Michael>    runs completely in supervisor mode (this was never
	Michael>    stated explicitly as far as I could tell; there
	Michael>    wasn't even an index entry for "supervisor").  Is
	Michael>    that deduction correct, and is it true for Mac
	Michael>    programs in general that everything is done in
	Michael>    supervisor state?

That's probably correct, but I don't recall for sure.

	Michael> 4. Isn't running solely in supervisor state a bit of
	Michael>    a lose?

Why do you say that?  It's a typical tradeoff of speed and efficiency
for protection.  For our purposes, we want it fast and small.  For
other projects, protection was more important, so multiple modes were
added.  It all depends on your requirements.

Shawn
-------------------------------------------------------------------------
Shawn Ostermann  -  PhD Student  -  Purdue Internetworking Research Group
  Internet:  sdo@cs.purdue.edu                  AT&T: (317) 494-7836
  UUCP:  {backbone}!purdue!sdo                  Fax:  (317) 494-0739
-------------------------------------------------------------------------

Newsgroups: comp.os.xinu
From: dls@mentor.cc.purdue.edu (David L Stevens)
Subject: Re: Availability of Xinu/tcpip distribution
Organization: PUCC UNIX Group
Date: Tue, 29 Sep 1992 19:05:59 GMT

	No, the TCP/IP software is not available via anonymous FTP. It is
available for sale through Prentice Hall, or, at a higher price, directly
from the authors. If you'd like more detailed ordering information, send
me e-mail and I'll be happy to send it to you.
-- 
					+-DLS  (dls@mentor.cc.purdue.edu)
Newsgroups: comp.os.xinu
From: johnr@pacdata.com (John Reed)
Subject: ctxsw posting
Organization: Pacific Data Products
Date: Mon, 5 Oct 1992 21:07:53 GMT


I just posted ctxsw.s for a generic 68000 CPU.  The file which was
posted had tabs set at every 4 columns (:ts=4), and looks a little
funny when read with the standard news reader.  Normally, I run
my postings through expand, but this time I forgot.

Sorry 'bout that!


JR


-- 


   /------------------------------------------------------------------\
  |  John Reed                           {ucsd,uunet}!pacdata!johnr    |
  |  Pacific Data Products               johnr@pacdata.com             |
  |                    ---------------------                           |
  |  George Herbert Walker Bush, with the letters re-arranged spells:  |
  |                                                                    |
  |                 Huge Berserk Rebel Warthog                         |
  |                                     -- From Cosmic Trigger II      |
   \------------------------------------------------------------------/
Newsgroups: comp.os.xinu
From: johnr@pacdata.uucp (John Reed)
Subject: Re: ctxsw routine for M68000
Organization: Pacific Data Products
Date: Mon, 5 Oct 1992 16:49:46 GMT

In article <1992Oct2.195944.772@nntpd2.cxo.dec.com> kgibsonkgibson@cxcad%decwrl.dec.com (Ken Gibson) writes:
>
>  Can someone post an M68000 version of the assembly language context switch
>routine _ctxsw for Xinu?  
>
>Many Thanks


*-----------------------------------------------------------------------------
* ctxsw  --	actually perform context switch, saving and loading registers
*		This routine is executed in kernel mode.
*
*		Upon entry, d0-d7, a0-a6, the usp, the sr, and the pc are
*		saved.
*
*		Upon exit, all registers saved are restored, and the value
*		of the user stack pointer is copied into the user 
*		stack pointer.
*-----------------------------------------------------------------------------

	section	14

	xdef	.cnt_ctxsw

.cnt_ctxsw	dc.l	0

	section	9

	xdef	.ctxsw

.ctxsw:
	addq.l	#1,.cnt_ctxsw
	move.l	a0,-(sp)	 		; Save A0 onto old stack	
	move.l	8(sp),a0			; Move address of old area into A0 
	movem.l	d0-d7/a0-a7,(a0)	; Save all registers		
	move.l	(sp),32(a0)			; Put original A0 in old savearea	
	addq.l	#8,60(a0)			; Move SP beyond return address
								; 	as if a return has occured
	add.l	#64,a0				; Skip past registers d0-7,a0-7
	move.w	#0,(a0)+ 			; Pad SR savearea, since SR is a word
	move.w	sr,(a0)+			; Save SR in old savearea
	move.l	4(sp),(a0)+			; Save PC in old savearea


*Save image:d0,d1,d2,d3,d4,d5,d6,d7,a0,a1,a2,a3,a4,a5,a6,ssp,0x00, sr, pc
*            0  4  8 12 16 20 24 28 32 36 40 44 48 52 56  60  64   66  68

	move.l	12(sp),a0			; Move address of new area into A0
	movem.l	(a0),d0-d7/a0-a6	; Restore all regs (even A0) except SP
	move.l	12(sp),a0			; Move address of new area into A0 again
	move.l	60(a0),sp			; Put  SSP into kernel stack
	move.l	68(a0),-(sp)		; Move PC onto current stack	
	move.w	66(a0),sr			; Restore the status register
	move.l	32(a0),a0			; Restore A0 from new area
	rts							; since we pushed the pc onto the stack,
								;   we just pretend to return






---JR---


-- 


   /------------------------------------------------------------------\
  |  John Reed                           {ucsd,uunet}!pacdata!johnr    |
  |  Pacific Data Products               johnr@pacdata.com             |
  |                    ---------------------                           |
  |  George Herbert Walker Bush, with the letters re-arranged spells:  |
  |                                                                    |
  |                 Huge Berserk Rebel Warthog                         |
  |                                     -- From Cosmic Trigger II      |
   \------------------------------------------------------------------/
From: kgibsonkgibson@cxcad%decwrl.dec.com (Ken Gibson)
Newsgroups: comp.os.xinu
Subject: ctxsw routine for M68000
Date: 2 Oct 92 20:43:19 GMT
Organization: Digital Equipment Corporation


  Can someone post an M68000 version of the assembly language context switch
routine _ctxsw for Xinu?  

Many Thanks
Newsgroups: comp.os.ms-windows.misc
From: skok@itwds1.energietechnik.uni-stuttgart.de (Holger Skok)
Subject: ARGHH!-WFW2.0 Sucks big time!
Keywords: Crashes problems wfw
Organization: Inst. f. Thermodynamik u. Waermetechnik (ITW), U. of Stuttgart, FRG
Date: Tue, 6 Oct 1992 10:49:56 GMT

Hi folks,

Anybody having similar experience with WFW2.0?
I have been working on a fairly large document and tried to split it up,
in order to improve response time and to make the handling of the files
easier. I divided the document into chapters and stored them in separate
files. Then I created a control file in which I entered the separate
chapters with the Insert File function. 
Using the proper display mode I could also see that the control file
indeed only contained a few headlines and the insertion fields. 
Imagine my surprise when I checked the size of the control file and
found it to be as large as the sum of all sizes of the inserted files!
(~3MB for a 46-page document containing many MS-Draw images)

I know that WfW2.0 does have trouble with importing images. Even though
there is a check box in the dialog to not include the image in the file
but to just reference the image file and only store its name in the WfW
- document, this doesn't work. Answer from MS-support: It's not a bug,
it's a feature.
But I hate that it's the same with the include file function. Am I
making some mistake?

Now with the 3MB-file I keep experiencing crashes. WfW manages to
violate memory protection. It's always the module GDI.EXE that's
affected. Any solution known to that problem?

My conclusion: I'll stay away from MS-products until they reach version
numbers 3.0 and greater.

HSK
-- 
Sie singen das alte Entsagungslied, das Eiapopeia vom Himmel,
womit man beruhigt, wenn es greint, das Volk, den grossen Luemmel.
Ein neues Lied, ein besseres Lied, oh Freunde, will ich Euch dichten,
Wir wollen hier auf Erden schon das Himmelreich errichten.    ... H. Heine
Newsgroups: comp.os.ms-windows.misc
From: varkki@ux1.cso.uiuc.edu (Varkki George)
Subject: Multimedia authoring tool
Organization: University of Illinois at Urbana-Champaign
Date: Tue, 6 Oct 1992 19:05:52 GMT

Are there available any high-level authoring tools for creating multimedia
Windows applications? Essentially, I am looking for the Windows
equivalent of Supercard (for the Mac).

R. Varkki George
-- 
Department of Urban and Regional Planning  | E-mail: varkki@uiuc.edu
University of Illinois at Urbana-Champaign | Tel:    217.244.7059
From: mam@mamunx.garmhausen.de (Michael A Meiszl)
Newsgroups: comp.os.ms-windows.misc
Subject: Re: ATI Graphics Ultra in 1024x768x256 Mode
Date: 4 Oct 92 07:08:52 GMT
Organization: Public Access Mailbox

In <JAMES.92Oct2171833@splinter.coe.northeastern.edu> james@splinter.coe.northeastern.edu (James E. Jones) writes:
>know if I am on the right track.  Does anyone else have problems with 
>ATI, QEMM and Windows?
The only problem I have encountered so far is that hitting ALT-CTRL-DEL won't
switch back to rom fonts but displays just boxes for all chars. I'm not
using QEMM but 386max. 1024x768x256 modes within windows works very well and
is fasssst.

The original poster may have the wrong driver installed. My ultra originally
came with 3.0 drivers which ran only with 512k installed on win 3.1.
Inserting more ram made windows go crazy. It could not switch to the graphic
screen anymore and sent you back to DOS immediatly. Installing new drivers
cured the problem. The ultra uses the same driver configuration for 16 and
256 colors.

	mam
-- 
** Michael Andreas Meiszl | Tomsonstr 25 | 4700 Hamm 1 | Tel +49 2381 889121 **
Newsgroups: comp.windows.ms.programmer,comp.os.ms-windows.misc,comp.os.ms-windows.programmer.misc
From: jimmy@namao.ucs.ualberta.ca 
Subject: SetCheck and Check/Uncheck on auto radio button
Keywords: Borland C++ 3.1, OWL, Windows 3.1
Organization: University of Alberta
Date: Tue, 29 Sep 1992 22:58:09 GMT


Hi,
I am trying to set the state of a radio button (auto) in a dialog
box in the dialog box's constructor. The reason is to set the radio
buttons to a specified settings when the dialog box comes up.
However, for some reason, Check/Uncheck and SetCheck(BF_CH.../BF_UNCH...)
are ignored and the radio buttons come up with random selections.
Why could this happen ? I can, however, easily change the radio
buttons using the mouse and then do a GetCheck on them.

Thanks,
Jimmy
Please email jimmy@namao.ucs.ualberta.ca

--
jimmy@namao.ucs.ualberta.ca
Newsgroups: comp.os.ms-windows.misc
From: gfini@nyx.cs.du.edu (Gianluca Fini)
Subject: Re: QEMM-386 and windows 3.1
Organization: University of Denver, Dept. of Math & Comp. Sci.
Date: Thu, 1 Oct 92 13:57:40 GMT

Yes Qemm386 si fully compatible with Win3.1
The only problem is that if You use it also as an EMS manager it slows down
your PC (the scroll in text mode and memory management).
Using himem.sys runs Your PC faster but You have to use emm386.sys to
obtain UMB (to load high programs) that has a lot of problems with a lot
of applications.