delorie.com/archives/browse.cgi   search  
Mail Archives: opendos/1997/03/04/12:50:50

From: MORRIS JP <jpmorris AT csm DOT uwe DOT ac DOT uk>
Date: Tue, 4 Mar 1997 12:51:10 GMT
Message-Id: <199703041251.MAA05605@milly>
To: opendos AT mail DOT tacoma DOT net
Subject: Re: [opendos] OpenDOS Startup logo [brannanp]
Sender: owner-opendos AT mail DOT tacoma DOT net

> From brannanp AT musc DOT edu Mon Mar  3 19:04:10 1997
> Date: Mon, 3 Mar 1997 13:37:13 -0500 (EST)
> From: Paul W Brannan <brannanp AT musc DOT edu>
> To: MORRIS JP <jpmorris AT csm DOT uwe DOT ac DOT uk>
> Subject: Re: [opendos] OpenDOS Startup logo
> Mime-Version: 1.0

Hmm, I may have started something big here.

> 
> Could you send me the source code for the startup logo program?  I think I
> have some ideas for the startup screen that I would like to try out.  I'm
> not up on my device driver coding, but I could get back into it.  Did you

The device driver was written by someone else.. that is the clever part.
The source is in A86, so it can be modified.

One possibility might be to make the int29 calls cycle part of the palette, to
allow for win95-type animations.  What I'd really like to do is get it to
write the messages to BOOTLOG.TXT.

Remembering that everything added to the device driver will eat up memory
and increase the size of the (tiny) hole at the start.

What I have done is in C, although it is quite simple stuff, I'll probably
convert it to NASM code tonight.

> use asm or c?  I think you have a nice idea here... one of the things that
> people hate about linux is that they think they are seeing error messages
> when the system boots when they are really just normal.
> 
> Paul
> 
> 
> 

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019