Re: [Unattended] question about freedos bootdisk image

[<Mat...@cb...>]

I still use the DOS boot disk images, since I don't have a linux machine 
or any linux knowledge to do any compiling.

They seem to work OK. I used the dos from Windows 95 SR2, and the 
himem.sys from Windows 95 as well. I also deleted the drvspace.bin file to 
make more room.
The freedos format doesn't seem to work for me, so I used the windows 95 
format, which works fine.

For your other question: Don't set the primary boot device to be pxe. If 
you can, add it as a boot device AFTER the HD. That way, you can delete 
the partition on the HD, and the next time the system boots, it will just 
fall to pxe. You don't want to try to actually modify the file on the 
server while you are using the PXE boot... Suppose you had more than one 
person using the PXE boot? It would mess it up for everyone else.








Thomas Seeling <tho...@gm...>
Sent by: una...@li...
09/26/2005 06:41 AM

 
        To:     una...@li...
        cc: 
        Subject:        [Unattended] question about freedos bootdisk image


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

Hallo,


from reading the list in the last few days I learnt
that the dos bootdisks are deemed deprecated.
Anyway, is anyone still using them?
I think they are much more convenient to customize
when compared to the linux boot disks and their
uncountable ;) prerequisites (with specific versions ...).

I have a strange problem where the bootdisk (real floppy) works fine,
but as soon as I make an image from this disk and use this
as my own empty-bootdisk.img for PXE booting, it stops working.
The symptom is that the config.sys is not used, i.e.
himem.sys and ifshlp.sys are not loaded.
No matter if I call the file config.sys or fdconfig.sys,
use plain msdos syntax or advanced freedos syntax ... it fails.
I added a minimalistic german keyboard driver (from 1991 c't),
and I can devload the ifshlp.sys, but then I don't have enough
memory to execute perl and spawned programs like fdisk.
devload.com hangs on loading himem.sys ;(
I even tried with original msdos 5, but this could not execute
perl at all.

A related question: if the primary boot option is PXE boot,
how do I prevent an infinite loop? Currently linuxboot-4.6
gets booted by PXE, WXP setup.exe configures the disk,
but even on the 2nd run it does not recognize that
the disk is already formatted and WXP waits to get booted
to continue the windows configuration.
Can I rename the tftpboot config file (the 32bit hex-IP filename)
somehow during or after the first run, so that the "default" file
can have localboot as 1st option?
Can PXE boot "look" at the hard disk and decide it's worth booting?
While playing with unattended I created a file C0A86420 manually
(for 192.168.100.32, my test machine) with localboot option
(and this works), but I'd like to have even this one automated ;).

Thanks in advance!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDN95t6tRbEjWup3IRAtFJAJ4vaBttBGjfhVOitNhoh8GmdYCNLwCgheyC
jWPEFS9JOAP8GIUrmu+kMdQ=
=cCuB
-----END PGP SIGNATURE-----



-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. 
Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
unattended-info mailing list
una...@li...
https://lists.sourceforge.net/lists/listinfo/unattended-info

NOTICE: The information contained in this email message, and any 
attachments accompanying this transmission, may be legally privileged 
and/or confidential and protected health information. This information is 
intended only for the use of the individual(s) and/or entity identified 
above. The authorized recipient of this information is prohibited from 
disclosing this information to any other party unless required to do so by 
law or regulation and is required to protect the information after its 
stated need has been fulfilled. If you are not the intended recipient, or 
an employee or agent responsible to deliver it to the intended recipient, 
you are hereby notified that any disclosure, printing, copying, 
forwarding, or distributing of this information is strictly prohibited. If 
you have received this communication in error, please notify the sender 
immediately, by telephone or return email, to advise of wrongful receipt 
and confirm your understanding of this Notice. Thank You.