===== AUTOMATIC NOTICE =====
Your email (attached beneath this notice) was blocked by my
email filter for one or more of these reasons:
* Your email came from or via a site whose email servers
(computers which process email) allow "relaying" or are
insecure in some other way, allowing senders of unsolicited
bulk email (usually called UBE, UCE or spam) to use
these servers to hide who they are and bypass filtering.
* Your email had headers or body text which looked like
spam to the my spam filter.
* Your email came from or via a site on the spam filter's list
of internet sites which allow users to spam, or which do not
take effective action against users which do so.
If you are a bulk mailer, advertiser (commercial or political), or
are sending any kind of "free offer", please remove this address
from your mailing list and do not email me again.
If you are not an advertiser or bulk mailer, you can resend your
mail and get past the filters by including the password listed
below on the Subject: line of your message. It can appear anywhere
on the Subject: line -- it doesn't have to be first, last, or the
only thing on that line.
An easy way to do this is to forward this bounced message back to
me and either change the Subject: line to the password, or add it
to the beginning or end of the Subject: line -- whatever is easier.
That way, I will get your email and be able to add your email
address to my NOBOUNCE list, which means email from you will not
bounce again. :)
Thank you!
********** The password is Planetoid. **********
=-=-=-=-=-=-=-=-=-=
>From netboot-owner@baghira.han.de Fri Mar 12 04:42:27 1999
Return-Path: <netboot-owner@baghira.han.de>
Received: from chgw-anathoth.anathoth.gen.nz (chgw-anathoth-eth0.int.anathoth.gen.nz [192.168.1.254])
by patmos.int.anathoth.gen.nz (8.9.3/8.9.3) with ESMTP id EAA12107
for <grantma@anathoth.gen.nz>; Fri, 12 Mar 1999 04:42:26 +1300
Received: from baghira.han.de (baghira.han.de [192.109.225.2])
by chgw-anathoth.anathoth.gen.nz (8.9.3/8.9.3) with ESMTP id EAA00619
for <grantma@anathoth.gen.nz>; Fri, 12 Mar 1999 04:42:20 +1300
Received: (from factotum@localhost)
by baghira.han.de (8.9.3/8.9.3) id KAA03006
for netboot-outgoing; Thu, 11 Mar 1999 10:11:02 +0100
X-Authentication-Warning: baghira.han.de: factotum set sender to owner-netboot using -f
Received: from voltron.flexstar.com (mail.flexstar.com [205.178.7.2])
by baghira.han.de (8.9.3/8.9.3) with ESMTP id KAA02626
for <netboot@baghira.han.de>; Thu, 11 Mar 1999 10:09:32 +0100
Received: from FTFL ([216.160.132.148]) by voltron.flexstar.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9)
id GV00S6N5; Thu, 11 Mar 1999 01:06:57 -0800
Message-Id: <3.0.1.32.19990311022456.00709c6c@pop.netaddress.usa.net>
X-Sender: mike-hammer@pop.netaddress.usa.net
X-Mailer: Windows Eudora Light Version 3.0.1 (32)
Date: Thu, 11 Mar 1999 02:24:56 -0700
To: netboot@baghira.han.de
From: Mike Hammer <mike-hammer@usa.net>
Subject: Re: Netboot not detected by system with PCI SCSI host adapter
In-Reply-To: <1999Mar8.124808.27847@gkminix.han.de>
References: <3.0.1.32.19990223011544.006d2f24@pop.netaddress.usa.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-netboot@baghira.han.de
Precedence: bulk
Reply-To: netboot@baghira.han.de
X-Moderator: netboot-owner@baghira.han.de
X-SpamBouncer: 1.00h (12/23/98)
X-SBRule: BULKTAG
X-SBRule: Free Email site
Hello there,
I've rebuilt the netbootrom using the option to *not* search for boot
disks and now Netboot has the chance to boot from the network past
the SCSI boot device. I guess i would like to clarify my understanding
of INT18H and IN19H once and for all.
>From the documentation that describes these interrupts, it seems INT18H
and INT19H are both sort of used for the same purpose, which is to allow
a bootable device (either bootable disk drive or network adapter with
on-board bootrom) to get boot'ed by the system ROM BIOS. If Netboot
only uses INT18H then it will *only* get called by the system ROM BIOS
when there's no bootable disk available. Only time the Netboot's INT18H
will get called is if there's not bootable disk installed in the system.
The odd thing is that my SCSI device was *not* a bootable disk, i.e.
there is no boot partition on it yet (i have not done fdisk and marked
a primary boot partition). Maybe the SCSI ROM BIOS is posting to the
system of bootable device being present regardless.
Anyways, by not using INT18H and rather INT19H, Netboot can be not
part of that exclusive chained list of system bootable/bootloader devices.
Thus last one to get chained into this list is the winner and
considered as system bootloader device.
So looks like the system ROM BIOS uses the INT19H first and if it
finds that there's no bootable device in this chain then it will
call down to INT18H.
PS. In regards to my past postings on testing of Netboot 0.9.0d version,
i could send you two SBC's (Single Board Computer) where one has
Realtek 8029AS right on the main board and the other having Realtek
8139A embedded. If you think this would help in your development and
work toward future releases, just let me know and i'll FedEx it
right to you. I would need your address though.
I haven't really had chance to look at Netboot 0.9.0d release
since i posted couple of the questions which the responses i got from
the listserv wasn't really helpful in solving the issues.
PSS. Previously i have posted the block0 froma typical Windows 95 (MSDOS7)
boot floppy. Is this helpful in adapting mknbi-dos to support
generating ramdisk from a file as opposed to from floppy?
Regards,
-mh
At 12:48 PM 3/8/99 GMT, you wrote:
>Hello,
>
>Mike Hammer <mike-hammer@usa.net> wrote:
>> Upon booting the sysstem, i can see on the screen that PCI SCSI controller
>> BIOS is displaying its banner message with etc but soon as that's complete,
>> i don't see the Netboot message at all. As if Netboot has been completely
>> bypassed by either system BIOS or SCSI controller BIOS.
>> [...]
>> So i guess i'm wondering why is that the presence of PCI SCSI adapter
>> BIOS causes Netboot to get not called by the system BIOS? Or am i seeing
>> a limitation with Netboot in dealing with other add-in adapter BIOS's in
>> the same system?
>
>Do you have a bootable disk connected to the SCSI adapter? If so, and you
>selected interrupt 18h handling during generation of the bootrom the BIOS
>will always load the operating system from the boot disk instead of calling
>netboot. In that case, you have to answer the makerom question "Do you want
>the BIOS to look for boot disks?" with "no", so that interrupt 19h will be
>used. Of course, it's still possible that the SCSI BIOS also redirects
>interrupt 19h after the netboot bootrom has done so. In that case, you
>should place the netboot bootrom on a ROM address higher than the SCSI
>BIOS, so that the bootrom initialization gets called after that of the
>SCSI BIOS and has a chance to redirect the interrupt properly. However,
>if you are using a farily new system with a BBS compliant BIOS I recommend
>to use version 0.9.0d of netboot, as it has full BBS support.
>
>gero.
>
>--
>Someone's been mean to you! Tell me who it is, so I can punch him tastefully.
> - Ralph Bakshi's Mighty Mouse
>--
>Gero Kuhlmann, Hannover 0511/6497525 (Voice) gero@gkminix.han.de
>===========================================================================
>This Mail was sent to netboot mailing list by:
>Gero Kuhlmann <gero@gkminix.han.de>
>To get help about this list, send a mail with 'help' as the only string in
>it's body to majordomo@baghira.han.de. If you have problems with this list,
>send a mail to netboot-owner@baghira.han.de.
>
DSS/Diffie-Hellman Key
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: PGPfreeware 5.0i for non-commercial use
mQGiBDY678URBADcwE2rJwU4H/uUOrOL/19dtB8Wz8kEGbu+ODM/OfW9xe1AYM/5
aeNyF3Ngt3m2MFTGqCKCV/HmyezMupo9Oy6MpKGdmaBnM1vke+ReZn6aN9bhxiqF
8YO9b6zwpeNUxHrTmAy21DEJsTHdlH0fEvqM4v8v6n4uAD0Qa5rAu/BQgwCg/5EK
2VUvrdEKt9Jg5ZvjDF1cNwMD/ip/cbQbu8fm2C2sX4SUNIItH47GStd+6t9u5imY
ARDkiBnKXxjmbc3h2uz5hQQm3JMrTsneOWr9lFkStTbf0zlzLq0T81pwGR+qdXfI
mZJVXxDb8xr6uFtpBlX4Ns8lbwyumcTHN/t5wCT03fuZxH0jamGk/5pQ7ikNkDGh
pEBZA/0cE4MGRlzRG/+MnyhmJy9WHWSAuOZ6ZCQrsIL/2SBWAj6AV21WY7rDaun2
/LR0068XpDMUo7ogKkthepaMa+aXYZbMQGKet2vS3gqmHoOwtLSCopsFb71RWOF3
sSmetbGIeTrYiUeywd90if/qJR8QAukudfqMP1UCK7SixDDC1bQgR2VvcmdlIFNo
aW4gPGdzaGluQGZsZXhzdGFyLmNvbT6JAEsEEBECAAsFAjY678UECwMBAgAKCRBR
2ylc3bRWhjD+AKDmZBtr6hIGuWQDVGGeO4WeCNQZdQCgh7w/45RVcBzAqpiMQM2X
lnzgDDS5AQ0ENjrvyxAEAMxWnRFgWEUSjf0txrdsM5vvSExPfMNL8rECaGQZnnlz
G1iTWF5gPb25LEyihMBcG3qInC5JVymZzcKCRchs0psGEUZkXas/w1nBpHGC/9p9
66rIlSGtjy/GDftxrjIvSWyyNwLndue4blnwBQ8sbpp5asjgQwA8yNz2tZW9gV5d
AAICA/0WjpRCB8Q28wV7b5nt0virsj+QyEh3IVjSKikRyJsI1sd9HiNxYzT3ibvN
kC626dhGjpa5gIJQEQ3fp6Br1hwsKqHqze7oh0ergx3XGLpYvG4dTlb4HGDCN0Hq
DEZ07C7QzYFzI87aP6zitayWY1kIlZocWQImYTrEQvCjCISxfYkAPwMFGDY678tR
2ylc3bRWhhECnhgAn3iwz3HvRk3p7Q5fCzwY0KUgllp6AJ46AOFlTgvOGCwxh+vZ
C8ypo3CvVg==
=mTPj
-----END PGP PUBLIC KEY BLOCK-----
===========================================================================
This Mail was sent to netboot mailing list by:
Mike Hammer <mike-hammer@usa.net>
To get help about this list, send a mail with 'help' as the only string in
it's body to majordomo@baghira.han.de. If you have problems with this list,
send a mail to netboot-owner@baghira.han.de.
===========================================================================
This Mail was sent to netboot mailing list by:
grantma@anathoth.gen.nz
To get help about this list, send a mail with 'help' as the only string in
it's body to majordomo@baghira.han.de. If you have problems with this list,
send a mail to netboot-owner@baghira.han.de.
For requests or suggestions regarding this mailing list archive please write to netboot@gkminix.han.de.