From owner-freebsd-questions Sat Nov 11 13:30:22 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA03307 for questions-outgoing; Sat, 11 Nov 1995 13:30:22 -0800 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA03302 for ; Sat, 11 Nov 1995 13:30:14 -0800 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA08077; Sat, 11 Nov 1995 14:24:59 -0700 From: Terry Lambert Message-Id: <199511112124.OAA08077@phaeton.artisoft.com> Subject: Re: Any info on Win95 boot process ? To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Sat, 11 Nov 1995 14:24:59 -0700 (MST) Cc: questions@freebsd.org In-Reply-To: <199511111319.OAA11756@labinfo.iet.unipi.it> from "Luigi Rizzo" at Nov 11, 95 02:19:37 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1904 Sender: owner-questions@freebsd.org Precedence: bulk > After trying out Samba... > > Does anyone have details on the boot process of Windows95 ? We > would like to set up a boot eprom for Win95, using the FreeBSD boot > eprom code as a starting point. > > Depending on how the bootstrap is carried on in Win95, the thing > might be very easy or very hard to do. It would be. You could do it, but it would take Level 2 or better access to materials. You would need at the very least the MSVC2.0, the SDK, and the DDK. The main problem isn't the bootstrapping, it's the switch to protected mode. Basically, the thing switches from a non-protected mode FAT FS (that you could intercept at the INT 21 or INT 13 level in your boot code, per your second scenario) to VFaT, which you couldn't unless you predisable 16 bit I/O, etc. Even then it's rather iffy when the thing first comes up; basically, you'd probably have to reimplement VFAT to make it happy, since it will call the VFAT FSD entry point FS_OpenFile with a NULL pir->ir_ppath to indicate that it's reestablishing a handle for a file that was open before it went into protected mode. > + otherwise, a small floppy image should be loaded somewhere in memory, > [so that the network card is not in use afterwards], the disk > read&write routines are hooked to some code which accesses this image > instead, and control is transferred to the standard boot code. > After booting has completed, the area of memory containing the floppy > image is freed and returned to the pool of usable RAM. > > The second approach is harder, because you have to find out how to > allocate memory in such a way that the floppy image is not overwritten > during the (early) stages of the boot process. It's also the onlt one with a chance of success. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.