Zitat von Radu - Eosif Mihailescu <radu.mihaile...@linux360.ro>: > Well, the only situation I came across that forced me to use the DOS > boot disk instead of the Linux one was a couple of laptops with very > new (read: weird) Marvel Yukon NICs that the kernel on the Linux > bootdisk did not have support compiled in for (or available as a > module). > > Of course, I could have rebuilt the Linux boot disk, but time was a > scarce commodity in both cases and restarting the procedure with the > DOS image (which got the job done just as well) seemed the natural > choice. > > @Dexter > > On 08/02/2009 11:12 PM, Patrick Benton wrote: >> >> oh. Didn't catch that. Guess I could have looked at the .imz file >> more closely. >> >> I guess the real question is -- why is he using a dos boot disk and >> not the linux boot? I'm just curious. Maybe he has some good >> reason to go the dos boot rout? >> >> **Patrick Benton** >> >> IT Specialist >> >> **Commnet Wireless LLC****** >> >> *_IT support_*_: _ >> >> 720-733-7688 >> >> itsupp...@commnetwireless.com <mailto:itsupp...@commnetwireless.com>__ >> >> *_Direct: _* >> >> 720-733-5373 >> >> pben...@commnetwireless.com <mailto:supp...@commnetwireless.com>__ >> >> P Before printing this document, please think about the environment >> >> ------------------------------------------------------------------------ >> >> *From:* Radu - Eosif Mihailescu [mailto:radu.mihaile...@linux360.ro] >> *Sent:* Sunday, August 02, 2009 2:03 PM >> *To:* unattended-info@lists.sourceforge.net >> *Subject:* Re: [Unattended] Problems with PXE and unattended-4.8 >> >> Patrick, >> >> He's using memdisk because he's using the DOS boot disk to start >> the installation. >> >> "undis3c.imz" is a 1.44MB floppy (80 cylinders x 2 heads x 18 >> sectors x 512 bytes each) image that is perfectly bootable with >> memdisk (albeit using 'keeppxe' on the command line to actually >> have it work once booted :-) ) >> >> The solution you are suggesting below pertains to the Linux boot >> disk (also the recommended method by Unattended's authors), not the >> DOS one. >> >> ------------------------------------------------------------------------ >> >> >> So, r...@krautmann.net <mailto:r...@krautmann.net>, please try to >> switch to the Linux boot disk and see if it solves your problem. >> >> >> Have a nice evening everyone, >> @Dexter >> >> > > > -- > @Dexter<radu.mihaile...@linux360.ro> GSM: +40 (721) 294400 > JID: csdex...@jabber.linux360.ro ICQ: 27762040 Y!: csdexter > MSN: rmihaile...@hotmail.com AIM: csdexter Skype: csdexter > Blog: http://www.linux360.ro/~csdexter/blog/
Hi newsgroup, I know I know....normally I would not do this, but because of the fact, that I cant get unattended.sourceforge working because memdisk doesnt load I give you a portforwaded access to my server directly to the root console (it is only a testserver that doesnt host any datas or something..) would be really nice if somebody could tell me why memdisk doesnt load. I installed the server now the 4. time and no changes. Always when a client boots I get the message: boot: b44 (e. g.) Loading unattended/memdisk...... Loading unattended/b44.imz....... Ready and than it hangs. If you want to help me go to your console and type in: telnet pxeshit.dyndns.org User: integralzerfetzer pass: pxeshit Then do two times cd.. and then you are in the root console where you can find the tftpboot directory. I hope somebody can help me and solve this problem because now i am searching since one week for a solution of this problem. Thanks in advance ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
