netboot-general — General discussion about the netboot project

[Netboot-general] Obtain a University Degree based on your professional experience.

[<net...@ms...>]

<hI align="center">A Genuine Univers1ty Degree in 4-6 weeks!</h1>
<div aIign="center"><br>
  Have you ever thought that the on1y thing stopp1ng you from @ great job @nd 
  better pay wa$ a few letters beh1nd you name?<br>
  Well n0w you can get them!<br>
  <br>
  <b><font size="+3">BA BSc M@ MSc MBA PhD</font></b><br>
  <br>
  <font $ize="+2"><b>Within 4-6 weeks!<br>
  No Study Requ1red!<br>
  100% Verifi@bIe!</b></font><br>
  <br>
  The$e @re real, genuine degree$ that include Bache]ors, Ma$ters, MBA @nd Doctorate 
  Degrees. They are fully ver1fiable and certif1ed transcr1pts are also av@1IabIe. 
  <br>
  <br>
  <b><font s1ze="5">Just call the number below.<br>
  You’II th@nk me later…<br>
  </font></b><br>
  <font c0lor="#FF0033" size="+2"><b>1-815-828-2222</b></font><br>
  24 hours a day, 7 days a week including Sund@y$ @nd Holid@ys<br>
</div><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><
BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR>coloured h@ir winked. And Hesti@ J0nes. A pink-

[Netboot-general] Netautomationpro Subscription Confirmation

[<in...@al...>]

Hello

Thank you for subscribing. Please confirm your subscription by clicking o=
nce on the link below or copying and pasting it into your browser.

http://www.all-ebizservices.com/cgi-bin/arp3/arp3-confirm.pl?c=3D267846&p=
=3D1130

Thank you.

[Netboot-general] Too busy to go back to school, but need a University Degree to get ahead?

[<ne...@bu...>]

<div align="left"><b><f0nt size="5"> Want the degree but can’t f1nd the t1me?</font></b><BR>
  <BR>
  WHAT A GREAT IDEA!<BR>
  We prov1de a concept that wi1l allow anyone with sufficient work exper1ence 
  <aco></aco>to obtain a fully verifiable University <acb></acb>Degree.<BR>
 <ack></ack> <acv></acv>Bachelors, Masters <acn></acn>or even a Doctorate.<BR>
  Think of it, within four to six weeks, you too could be a <acn></acn>college graduate.<BR>
 <acu></acu> Many people share the same frustration, they are all doing the work of the person 
  that has the <act></act>degree and the person that has the degree is getting all the money.<BR>
 <acm></acm> Don’t you think that it <acj></acj>is time <acw></acw>you <acs></acs>were paid fair <ach></ach>compensation for the <acj></acj>level 
  of work you are already doing?<BR>
  This is your chance to <aca></aca>finally make the right move and receive your due benefits.<BR>
  If you are like most people, <acq></acq>you are more than <acs></acs>qualified with your experience, <ace></ace>
  but are lacking that prestigious piece of <acz></acz>paper known as a diploma that is often <acc></acc>
  th
e passport to success.<BR>
  <b>CALL US TODAY AND GIVE YOUR WORK<BR>
  EXPERIENCE THE CHANCE <acc></acc>TO EARN YOU<BR>
  THE HIGHER COMPENSATION YOU <acr></acr>DESERVE!</b><BR>
  <font color="#FF0033" size="5">CALL NOW:</font><font color="#FF0033" size="7"><BR>
 <ace></ace> <b>1-815-828-2222</b></font><BR>
 <aca></aca> <BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <acu></acu><BR>
  <BR>
  <acn></acn><BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <acm></acm><BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <acf></acf><BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <BR>
 <acu></acu> <BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <ack></ack><BR>
  <BR>
  <BR>
 <ack></ack> <BR>
  <BR>
  <BR>
  <BR>
 <aca></aca> <BR>
  <BR>
  <acu></acu><BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <ack></ack><BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <acv></acv><BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <aci></aci><BR>
  <BR>
  <BR>
  <BR>
 <act></act> <BR>
  <acs></acs><BR>
  <BR>
  <BR>
  <BR>
  <BR>
  <BR>
 <ack></ack> <BR>
  <acq></acq><BR>
  <BR>
  <BR>
 <acq></acq> <BR>
  <BR>
  <BR>
 <ack></ack> <BR>
 <ace></ace> <BR>
  <BR>
  <BR>
  <acu></acu><BR>
   standing furthest 
back - he had a deep, slow voice and wore </div>
 

[Netboot-general] We're all fucked. It helps to remember that

[harrison d. <ec...@ju...>]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Liverpudlian</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
</HEAD>
<BODY>

<b>Howdy!</b><br>
<div align="center">
<IMG src="cid:53D40CE1.F627A89B.53D40CE1.F627A89B_csseditor" border="0" width=340 height=255><br>
<strong><font size="5" face="Verdana, Arial, Helvetica, sans-serif">
nifed<font color="#CC0000">[dot]</font>com</font></strong><br>
<br><br>----
<p>finger, the priest said the same thing.
And the bridal pair tried several times to understand what they
had to do, and each time made some mistake and were corrected by
the priest in a whisper.  At last, having duly performed the
ceremony, having signed the rings with the cross, the priest
handed Kitty the big ring, and Levin the little one.  Again they
were puzzled, and passed the rings from hand to hand, still
without doing what was expected.
Dolly, Tchirikov, and Stepan Arkadyevitch stepped forward to set
them right.  There was an interval of hesitation, whispering, and
smiles; but the expression of solemn emotion on the faces of the
betrothed pair did not change: on the contrary, in their
perplexity over their hands they looked more grave and deeply
moved than before, and the smile with which Stepan Arkadyevitch
whispered to them that now they would each put on their own ring
died away on his lips.  He had a feeling that any smile would jar
on them.
"Thou who didst from the beginning create male and female," the
priest read after the exchange of rings, "from Thee woman was
given to man to be a helpmeet to him, and for the procreation of
children.  O Lord, our God, who hast poured down the blessings of</p>
<br>
</div>

</BODY></HTML>

[Netboot-general] Image Download Problem (block 1067)

[basil <el...@ce...>]

Hello,
my boot process stops when it is downloading the boot rom.
The last 4 lines say
Options: Blocksize 512
Block 1067
Bootrom error: PXE-20
Network boot failed.

I have read a thread that spoke about the same problem at this list. But 
the solution is not  so   good (to chacnge my network card). Althought i 
dont have the same model. Mine is Realtek 8139.
ANyway some more information.
Memory size 49152 Kbyte. No use of ramdisk . I am using nfs share. CPU 
pentium mmx 166. Award Bios 4.51PG.
The ethereal spying shows that the last packet sent is 1070 and as a 
reply it doesnt get an acknowledgement (as previous packets did) but an 
error message saying : Disk full or allocation exceeded [Malformed 
Packet].. Then follows an ARP request from the server of the clients 
MAC. End.

And a note. You see above (in the error message ) it says BlockSize 512. 
But spying the negotiation with Ethereal one can see at the begining 
that the client says: TFTP read request [............]  Option: blksize 
= 1432, Option tsize =0. What is this blksize? And why is it different 
from the Blocksize Message issued at the screen of the client?


basos

[Netboot-general] =?iso-2022-jp?B?IBskQkJ0MGYkRyQ5GyhC?=

[<ne...@ci...>]

DQobJEJGTUEzJE4lYSE8JWskRz89JDdMdSQ0JDYkJCReJDskcyEjO2QkTyU7JWwlVjZmM1pJdCRI
JCQkJkE0OXFFODMrJE4jMyMwQmUwSj5lJE40ezonPFQkLD04JF4kayEiJTMlXyVlJUslRiUjJHJF
fTNnJDckRiQkJGtCdDBmOSVIfiRIPz0kNyReJDkhIzRKQzEkS0BiTEAkJCQ/JDckXiQ5JEghIj9N
OkokTj13QC0kLDAmP00kckM1JDklMyVfJWUlSyVGJSMkRyQ5ISMkPSROJGgkJiRKNFg3OCRLNj1M
IyROJCIka0NLQC0kTyUzJUElaSReJEclIiUvJTslOSQ3JEYyPCQ1JCQbKEIgGyRCJTMlQSVpISEb
KEJodHRwOi8vYXdnLndlYmNodS5jb20vY2FzYW5vdmEvPzE5MzQbJEIhISRHJTslbBsoQiANChsk
QiVWNmYzWkl0JEg4ITp3JDckRiRiJGkkKCRsJFA9d0AtJE40aTxMPz9JVSQtJE4lVyVtJVUlIyE8
JWskSE8iTW1AaCRyOCskazt2JCwkRyQtJF4kOSEjJCpCVCRBJDckRiQqJGokXiQ5ISMbKEINCg0K
DQoNCg0KLy8vLy8vLy8vLy8vLy8vLy8vLy8vLy8vLy8vLy8vLy8vDQobJEIlYSE8JWtJVE1XJE5K
fSRPJDMkQSRpJEslYSE8JWskciItGyhCDQpjb25jZXB0M19uZXRAeWFob28uY2ENCg0KDQo=

[Netboot-general] New netboot version 0.10

[Gero K. <ge...@gk...>]

Hello,

after more than two years of work I'm pleased to announce the release of
netboot version 0.10. This release has been tested on many different
host
systems and with various different network cards to improve
compatibility.
However, the most important change has been the move from the old bin86
tools towards using GNU development tools. It is now possible to compile
all client code using GNU tools, even on non-x86 systems by using a
cross
compiler. Therefore, most changes in this release are not directly
visible
to the user. Among the new noticeable features are:

	General:
		- support for different backends to access the systems
		  database: plain text database files and Berkeley DB
		  are currently supported, ODBC and LDAP are planned
		- support for writing into the systems database with all
		  utility programs
		- support for writing log files with all utility programs
		- better support for different character sets
		- libtool support: it is now possible to compile a
		  shared library for all the utility support routines
		- completely removed support for pre-386 processors, so
		  everything is 32-bits now

	Bootrom:
		- support for multicast TFTP transfers (still untested)
		- full support for DHCP with netboot extensions
		- full support for PXE API
		- support for generic network drivers

	Makerom:
		- makerom is now able to install new network drivers into
		  the proper place thus eliminating the need to manually
		  copy and edit anything in order for a network driver to
		  appear in the menu
		- saving bootrom definitions into the systems database
		  without editing any database files manually
		- supports writing a bootrom image which can be included
		  into a system BIOS (however, this requires additional tools
		  which are not part of the netboot package)
		- many changes to the user interface, including the display
		  of help texts

	mknbi-dos:
		- support for using a compressed ramdisk in order to reduce
		  download time of DOS netboot images

	mknbi-linux:
		- support for Linux kernel 2.6.x

	mknbi-mgl:
		- support for multiple image loaders: mknbi-mgl now contains
		  a new image loader which allows an MGL boot image to get
		  downloaded using a commercial PXE bootrom. This way it is
		  possible to use such commercial PXE bootroms with other
		  netboot boot images generated with mknbi-linux or mknbi-dos
		- various MGL syntax cleanups and improvements like some
		  missing programming constructs and pointer types
		- support for MGL include files
		- lots of bug fixes in the MGL runtime code

The only thing which is still missing is a comprehensive documentation.
Even
though I have updated the existing documentation (especially the man
pages)
to reflect all changes, a user's manual which puts all pieces together
is still
missing. This is planned for one of the next releases.

Until then, have fun with netboot, and please let me know if you find
any bugs
or have any ideas for improvements.

My sincere thanks go to all the many people who have helped me with
improving
this release, and who are too numerous to mention here.

gero.

--=20
Gero Kuhlmann                                      Groote Gracht 33
ge...@gk...                                26723 Emden
ge...@gk...                                    Tel.: 04921/997561

AW: [Netboot-general] Probs with netboot/NFS

[Gero K. <ge...@gk...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

> -----Urspr=FCngliche Nachricht-----
> [...]
> Kernel command line: auto rw root=3D/dev/nfs nfsroot=3D/nfsroot
> ip=3D192.168.1.18:192.168.1.2:192.168.1.1:255.255.255.0:
> <etc>
> devfs: boot_options: 0x1
> <etc>
> RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
> eepro100.c:v1.09j-t 9/29/99 Donald Becker <url>
> eepro100.c: $Revision: 1.36 $ 2000/11/17 <etc>
> <etc>
> IP-Config: Complete:
> device=3Deth0, addr=3D192.168.1.18, mask=3D255.255.255.0, gw=3D192.168.=
1.1,
> host=3D192.168.1.18, domain=3D, nis-domain=3D(none),
> bootserver=3D192.168.1.2, rootserver=3D192.168.1.2, rootpath=3D
> <etc>
> RAMDISK: cramfs filesystem found at block 0
> RAMDISK: loading 1156 blocks [1 disk] into ram disk... done
> <etc>
> Kernel panic: VFS: Unable to mount root fs on 00:ff
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> (note nothing set after "rootpath" in the IP-Config bit)

Automounting a root-NFS file system is a two-step process: first the
kernel has to configure the network interface, and then it has to call
the NFS code to actually mount the root directory. Configuration of the
network interface is done using the "ip=3D" command line option. If this
option is missing, the kernel sends out its own DHCP/BOOTP/RARP requests
to configure the interface, and it then sets the "rootpath" using the
information it got from the server. In your case, the bootrom already
did all that BOOTP thing, and passed a valid "ip=3D" option to the kernel.
The kernel therefore had no need to start DHCP itself, and therefore the
"rootpath" value in the debugging output is empty. This is OK, and your
network interface has been setup correctly.
The second step involves mounting the NFS root directory. The name of
the directory is taken from the "nfsroot=3D" command line option, which
has also been passed correctly by the bootrom process. Unfortunately, you
did not give us any kernel output which relates to the NFS step. I there-
fore assume that you did not compile your kernel using nfsroot support.
Please check for the CONFIG_ROOT_NFS variable being set in your kernel
configuration file (/usr/src/linux/.config). Set this to "y" and recompil=
e
the kernel.

> [...]
> The command I used to make the .nbi file is:
>
> mknbi-linux -x -d /nfsroot -i rom -r initrd.img-2.4.32.img -k bzImage -=
o
> bootImage.nbi

With this command line you specify the root directory explicitely. You
can also use "-d rom" to the let the bootrom set the root directory
according to the information in the BOOTP/DHCP response.

Please let me know if this answer did not solve your problem.

gero.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)

iD8DBQFDq9hA8f/CfZ6W4egRAlprAJ9rJ1YOgRQGe9qSsJOT/KXPSDkkFQCgjbvx
XhhiYhHkK5XQlVF5L8Y2rvk=3D
=3D7qXe
-----END PGP SIGNATURE-----

[Netboot-general] Probs with netboot/NFS

[Piers K. <de...@bi...>]

Hello all,

Am trying to boot a diskless client with the following spec:

Gigabtye GA-6BXE
256MB PC133 RAM
Slot 1 Intel Pentium 3 666MHz at 133MHz FSB
Intel Ethernet Pro 100B network card
Geforce MX4000 video card

It downloads the 2.4.32 kernel from my server and boots, but when it 
tries to mount the root filesystem, it fails.  I suspect the problem is 
that it isn't trying to mount it via NFS as there's nothing in the 
server logs that shows the client is trying to mount the root filesystem 
  via NFS.

The failing message is:

=================================
Kernel panic: VFS: Unable to mount root fs on 00:ff.
=================================

The message output by netboot is:

=================================
BOOTP: Sending request (press ESC to abort): ok

Local IP: 192.168.1.18
Server IP: 192.168.1.2 ()
Gateway IP: 192.168.1.1
Loading /bootImage.nbi
Options: Blocksize 512
Block 4183 ok

Starting image...

Linux Net Boot Image Loader Version 0.9.8 (netboot)
(copyright notes)

Uncompressing Linux... Ok, booting the kernel.
Linux version 2.4.32-pk-20051220 (root@desire) (gcc version 3.3.5 
(Debian 1:3.3.5-13)) #1 Tue Dec 20 17:51:13 GMT 2005
=================================

And the messages found in the bootup list that I think are important are:

=================================
Kernel command line: auto rw root=/dev/nfs nfsroot=/nfsroot 
ip=192.168.1.18:192.168.1.2:192.168.1.1:255.255.255.0:
<etc>
devfs: boot_options: 0x1
<etc>
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
eepro100.c:v1.09j-t 9/29/99 Donald Becker <url>
eepro100.c: $Revision: 1.36 $ 2000/11/17 <etc>
<etc>
IP-Config: Complete:
device=eth0, addr=192.168.1.18, mask=255.255.255.0, gw=192.168.1.1,
host=192.168.1.18, domain=, nis-domain=(none),
bootserver=192.168.1.2, rootserver=192.168.1.2, rootpath=
<etc>
RAMDISK: cramfs filesystem found at block 0
RAMDISK: loading 1156 blocks [1 disk] into ram disk... done
<etc>
Kernel panic: VFS: Unable to mount root fs on 00:ff
=================================

(note nothing set after "rootpath" in the IP-Config bit)

The messages in the server logs include:

=================================
Dec 20 20:12:37 destiny dhcpd: BOOTREQUEST from 00:a0:c9:9b:99:ba via eth0
Dec 20 20:12:37 destiny dhcpd: BOOTREPLY for 192.168.1.18 to hinata 
(00:a0:c9:9b:99:ba) via eth0
Dec 20 20:12:37 destiny in.tftpd[14338]: connect from 192.168.1.18 
(192.168.1.18)
Dec 20 20:12:37 destiny tftpd[14339]: tftpd: trying to get file: 
/bootImage.nbi
=================================

The snippets from dhcpd.conf are:

=================================
option root-path "/nfsroot";
next-server 192.168.1.2;
filename "/nfsroot";

host hinata {
         hardware ethernet 00:A0:C9:9B:99:BA;
         fixed-address 192.168.1.18;
         filename "/bootImage.nbi";
}
=================================

bootImage.nbi is stored in /

The command I used to make the .nbi file is:

mknbi-linux -x -d /nfsroot -i rom -r initrd.img-2.4.32.img -k bzImage -o 
bootImage.nbi

Although I note if I use:

mknbi-linux -x -d ram -i rom -r initrd.img-2.4.32.img -k bzImage -o 
bootImage.nbi

I get a different panic message:

=================================
Kernel panic: VFS: Unable to mount root fs on 01:00
=================================

but that is the only difference I get.  Is 01:00 better than 00:ff ?

Also how do I solve either problem?

Thanks very much for your help in advance

Regards - Piers

Re: [Netboot-general] General questions about boot roms, booting off network on older systems

[Peter <pl...@ac...>]

The ROM on the card is detected as a BIOS extension by the BIOS during 
equipment check. It has a particular signature and other features for 
this. Very often there is a message on the screen to this effect, 
emitted by the code in the extension ROM.

If it is detected correctly then it is executed by the BIOS. Apparently 
yours isn't for some reason. Things worth checking:

1) is the rom fast enough. Modern computers require 100nsec ROMs
2) is the card irq and io address correct for your setup
3) does the nic work
4) is the rom boot enabled (jumper on nic card or software switch in 
nic setup utility program run from DOS boot disk)

Peter

[Netboot-general] General questions about boot roms, booting off network on older systems

[James S. <js...@cp...>]

Please note, i am not using any ROMS made from netboot images!  I am 
using a card with a boot rom from Intel!
I am just asking for general help on the issue of booting a machine on 
an ethernet.
*************************************************************

Hello, today my professor has given to me a few old EISA Intel 
Pro/10mbps ethernet cards.  They use the Intel FA82595TX chip-set, and 
all of them contain what my professor says is a boot ROM.  The boot rom 
has the Intel Logo and "352226-001" on it, and is in a 32 pin 
connector.  I assume this is the boot rom.

The reason i asked my professor for these cards with the boot roms is so 
i can create a diskless workstation. I have never worked with these 
older boot roms; this is my first shot.

Anyway, when i got home, I plugged one of the cards into an ATX 
machine.  The BIOS on this machine has no "boot from nic," but i dont 
think that is an issue when working with these older NICs with boot 
roms.  Then again, i know nothing about this issue.  Anyway, as the 
computer goes through the boot strap, I see nothing to do with the ROM 
being used to boot over network.  At this point i decide to shut the 
comptuer off.

Should older boot-enabled NIC's on a motherboard with a bios that has no 
"boot from network card" feature show me anything during start up?  How 
does the computer know to attempt booting from the nic?  How is it 
supposed to be aware of the Network cards ability to contact a BOOTP 
server/TFTP server?  How were those computers i saw 10 years ago know to 
boot from the NIC?  I can be assured there bioses did not support a 
"boot from network card" option (i did not see this until recent). 
**confused** How on earth does the clients boot process know to boot 
from LAN when there is a boot rom, but no "boot from lan" field in the 
bios configuration?



Disregarding the fact i did not see any startup messages, I connected 
the boot rom card to what will be the BOOTP/TFTP Server via crossover 
cable, and ran a packet analyzer  on the server.  I powered on the 
client with the  Intel Pro/10 boot-rom enabled card, and watched the 
packet analyzer on the servers display. All that happened was the server 
(not running BOOTP or TFTP as of yet) did a few broadcast ARP requests 
as it noticed there was a link present.  The Intel Pro/10 responded with 
nothing, and there were not any ARP entries on the server.

I continued to let the client search for boot devices, and ended up with 
nothing except "invalid  system disk".

What i wonder now is, if a servers interface was configured for BOOTP 
and upon a link between it and a client with a boot rom was made, would 
the BOOTP server start a conversation, or would the boot rom software 
initiate?  Does a BOOTP server wait for a link to come up and then ask 
the boot rom for its mac address, or vice versa?

Oh well, you can see i have no experience with this issue. How am I 
supposed to know whats going on when the client gives no output on 
startup as to wether or not its trying to boot from nic?  Why doesnt the 
NIC send out any frames when i start the machine up?  Please someone 
give me general theories as to how these things work.

Sorry for all the newbie questions, but I really want to start making 
use of these nics my professor has given to me.

[Netboot-general] Re: [Etherboot-users] re: netboot problem (update: solved in a fashion)

[Peter L. P. <pl...@ac...>]

I managed to first use netboot-0.8.1 from Suse 6.1 (~1998) to generate a 
floppy image for ne2000 generic (my target uses a rtl8019 (as) nic card), 
running on a 2.2.16 suse kernel (it would not build on a 2.4 kernel). In 
addition to working right out of the box, the rom image fits in 16k 
instead of 32k needed by etherboot and modern (0.9.8) netboot rom images.

Then I managed to compile netboot-0.8.1 (including roms) on the same suse 
6.1 machine (2.2.16 kernel), but only after getting a modern (not 
contemporary with suse 6.1, the tools supplied with suse 6.1 failed to 
build the netboot package, esp wrong as86 version) version of linux86 
devtools (as86, bcc etc), namely linux86-0.16.14 and compiling and 
installing it on the old suse machine. Then I had to fix several errors in 
netboot-0.8.1 assembly files (duplicate labels and wrong or obsolete bcc 
and as86 options).

I can now boot 'old' clients with cheap isa nics from a more modern 
server, and I can build my own roms (I need small modifications, like try 
again forever on error and some hardware initialisation).

This confirms that the problem with netboot-0.9.8 is software. I was never 
able to make a rom image that booted a floppy, regardless of the source 
floppy I used or the target nic or the machine used (including not the one 
I used with 0.8.1 above, which worked immediately). Network transfer and 
dhcp/arp resolution works but no image is run (I tried 4 different dos 
floppy images).

Finding the correct package versions was painful and un-debian-like since 
the dependency listing (f.ex. for the netboot package) on the debian.org 
package listings does not mention the dependencies. There should really be 
a list of things that work with each other, at the netboot or etherboot 
project sites imho.

Again:

knoppix hd install/debian testing/unstable, with gcc3.3.3 was unable to 
build a working rom floppy using etherboot for rtl8019 target nic, the 
floppy causing hang on boot when built from source and wrong image message 
when using the version from rom-o-matic. I had to revert to netboot-0.9.8 
which also failed to compile and then to 0.8.1 which worked as binary and 
could be compiled after some debugging.

Comments are welcome,

Peter

[Netboot-general] re: new to netboot: mknbi-dos unable to boot any image

[Peter L. P. <pl...@ac...>]

Hi all,

I have netboot 0.9.8 (after trying etherboot unsuccessfully for my rtl8019 
slave cards). It installs & works but:

netbooting (with floppy) any image prepared with mknbi-dos fails, after 
the image transits the network. The error I get is always the same:

Starting image...

DOS Net Boot Image Loader Version 0.8.1 (mknbi-dos)
GPLed by G. Kuhlmann

Wrong ramdisk image

Network boot failed

// what means 'Wrong ramdisk image ?!

I tried dos5, dos6.22 and win95 and win98 rescue disk images (1.44Mb 
each), as well as a single floppy linux distro (that should also work 
imho).

What gives ?

I have installed netboot using ./configure; make; make install . I have 
gcc 3.3.3 (debian testing/unstable). There seems to be an issue with my 
toolchain as it fails to build etherboot images that behave like 
rom-o-matic (there may be no support for <i586 in the compiler toolchain 
!).

help ? tia,

Peter

[Netboot-general] netboot 0.9.8: mknbi-dos fails to boot dos and other images

[Peter L. P. <pl...@ac...>]

I have installed netboot 0.9.8 and made a floppy rom for my nic card. I 
have tftpd and dhcpd running. I made several images of floppies with dos5 
boot, dos 6.22 boot, win 95 boot and win 98 boot with mknbi-dos. All are 
loaded via tftpd and each gives the error 'incorrect boot image' *after* 
loading from the network. Transfer and messages etc suggest the images 
transit correctly, and in whole. Any ideas ?

thanks,

Peter

[Netboot-general] EthernetExpress 16

[Aldo L. A. <agu...@y2...>]

Hi, 

	I'm trying to boot with an EthernetExpress 16, and it gives me the
error:
82586 did not respond to command on the EtherExpress board

Somebody could meke work this cards?

Thanks in advance.

Luis

[Netboot-general] Booting Windows CE

[Roberto F. B. <ro...@td...>]

Hello,

  I am installing a diskless x86 workstation using Windows CE.
It has PXE features and it gets IP address through DHCP 
server. I've also installed a TFTP server. Both DHCP and
TFTP servers are working fine.
  I created a nk.bin image for WinCE using MS Platform Builder, 
but I can't make the workstation download it. The file nk.bin
is the WinCE kernel image. So I need to put it on the memory 
and run it.
  I know I need to use a boot loader to do that. I tried to
generate a ROM image using rom-o-matic. It runned fine but I 
could'nt make it download and run nk.bin.
   
  Can you, please, help me ?

Thank you very much.

Roberto


-- 
---------------------------------------------------------
Roberto Ferreira Brandao
High Performance Systems Engineer
TDI Electronics Brasil
Rua Guapuruvu - 160 - Alphaville Empresarial
13098-322 - Campinas - Sao Paulo - Brazil
Tel: +55-19-3296-4999 - e-mail: ro...@td...

[Netboot-general] Problem Netbooting 3c589

[ED <ed...@am...>]

Network card is Etherlink III PC CARD

Problems with  Boot Prom 3c589.com

Hey All,

Been trying to get Netboot going on an older laptop here.  The laptop can
no longer see its hardrive, ohterwise still works fine.  I was hoping to
use netboot to turn it into a nice portable X-Terminal.

First
Has anyone experiance with this card?  It seems as though others have got
it to work, but still a little unsure.

 My problem is with the packet driver.  I am using 3c589.com which came
 with the card install disk.  Diagnostics on the card show it at I/o 300h
 and INT 10.

 I don't know how to pass this info to netboot.  When the startup disk
 boots.  I get two messages, one is LSL not started.  That comes from the
 packet driver direct, either with the netboot disk or straight from dos.
 The other message is Packet driver error: no INT.

 I know I need to tell NETBOOT the interupt and the IO address but dont
 know the command line format.  I understand this should be whatever I
 would tell the packet driver under dos but can find no documentation of
 this.  And I dont see this message when I start the 3c589.com from dos.

 I am not even completly sure this is a packet driver.  Anywone got
 any clues.

 Thanks for anyhelp,

 First time Netbooter,

 ED
>
>
>
>

[Netboot-general] (Newbie) How to make a boot image which contains sub-dir?

[Eddy <ed...@si...>]

SSd2ZSBtYWRlIGEgYm9vdCBmbG9wcHkgd2hpY2ggY29udGFpbnMgYSBzdWItZGlyZWN0b3J5IGFu
ZCBoYXZlIGNvcGllZCB0aGUgZnVsbCBjb250ZW50DQpvZiB0aGlzIGRpc2sgaW50byAvaG9tZS9l
ZGR5L2Zsb3BweS8uIChUaGVyZSBpcyBhIHN1Yi1kaXIgb2YgL2hvbWUvZWRkeS9mbG9wcHkvbXlk
aXIvKQ0KVGhlIHNpemUgb2YgZmlsZXMgdW5kZXIgL2Zsb3BweS8gaXMgNjAwSywgdGhlIHNpemUg
dW5kZXIgL2Zsb3BweS9teWRpci8gaXMgOTAwSy4NCk5vdyBJIHdhbnQgdG8gbWFrZSBhIGJvb3Qg
aW1hZ2UgZnJvbSBpdC4gQnkgdXNpbmc6DQogIG1rbmJpLWRvcyAtciAvaG9tZS9lZGR5L2Zsb3Bw
eSAtbyBteWltYWdlLngNCkkgZ290IGFuIGJvb3QgaW1hZ2Ugd2l0aCBvbmx5IDYwMEsuIFRoZSBz
dWItZGlyIGlzIHNraXBwZWQ/Pz8/Pz8gV2h5Pw0KSG93IGNhbiBJIG1ha2UgYW4gaW1hZ2Ugd2hp
Y2ggY29udGFpbnMgdGhlIHN1Yi1kaXI/DQoNClRoaXMgaXMgbXkgZmlyc3QgdGltZSB0byB1c2Ug
bWtuYmkuLi4gTmVlZCBoZWxwLi4uLg0KDQo=

Re: [Netboot-general] Intel E100B "NDIS environment invalid" Error

[Jarrett R. <jar...@ya...>]

Sorry to bother you guys... I just downloaded etherboot and it boots just fine,
same environment, same everything.  Thanks anyway...


--- Jarrett Redd <jar...@ya...> wrote:
> I'm trying to get an Intel PRO/100B PCI card (type 80 on makerom menu) to
> work with netboot (I have version 0.9.1).


=====
Jarrett L. Redd (KG6ELZ)

__________________________________________________
Do You Yahoo!?
Yahoo! Greetings - Send FREE e-cards for every occasion!
http://greetings.yahoo.com

[Netboot-general] Intel E100B "NDIS environment invalid" Error

[Jarrett R. <jar...@ya...>]

Hi folks... been at this for 2 days straight, trying everything I can think of.
 Now I'm out of ideas.  Can anyone here help?

I'm trying to get an Intel PRO/100B PCI card (type 80 on makerom menu) to work
with netboot (I have version 0.9.1).  So far I am still trying with the floppy
image.  When I try with the netboot-provided packet driver, everything loads
just fine (correct MAC address, etc), but then hangs at the point where it says
"Found packet driver at int 62, irq 0A", right before the BOOTP attempt. 
Sometimes, if I unplug the network cable and plug it back in again, then
"BOOTP:" appears, but I don't see "Sending request..." and no connection is
made.

So then I tried to use an Intel-provided NDIS driver (e100b.dos) as I can't
seem to locate a packet driver for this card.  With NDIS, I see the driver load
(v4.27), but then it says "Failure: Driver did not load, NDIS environment
invalid".  I'm using a protocol.ini file that looks like this:

[E100B_NIF]
drivername = E100B$

"E100B_NIF" is the protocol.ini name listed for this card by Intel, and a
strings on e100b.dos shows this name as well.  However, makerom will not accept
the "E100B_NIF" section name without modifications.  It does not like the
underscore.    After the modification to accept the underscore, makerom is
happy, but then I get the afore-mentioned "NDIS environment invalid" at load
time.

(Background info:  I'm using an isolated network, 2 machines on a hub, the
server running Linux with dhcpd and tftpd.  I have tested both dhcpd and tftpd
and they work just fine outside of netboot.  In fact, using netboot with a
linksys etherfast 100 PCI card, I get the correct IP address from dhcpd and I
also get the correct tftp filename.  However, it then hangs trying to get the
file (UDP-read-timeout).  However, in the same environment with my netboot
client running linux on a local disk (no netboot), I can easily tftp the same
file.)

Anybody have any ideas on any of this?  Thanks VERY MUCH for your time...


=====
Jarrett L. Redd (KG6ELZ)

__________________________________________________
Do You Yahoo!?
Yahoo! Greetings - Send FREE e-cards for every occasion!
http://greetings.yahoo.com