Re: [Unattended] Problems with PXE and unattended-4.8
Hi, once again I have installed my system new and I have again the problem that memdisk doesnt load when a PXE client starts to boot. Again the message: Loading unattended/memdisk... Loading unattended/fetnd.imz...(This image works with this network card) Ready. But memdisk doesnt start ! Because I am very very confused about it I give you for tonight and tomorrow root access to my server. I hope somebody could tell me where the problem is. I have the memdisk and pxelinux.0 file from the unattended-4.8 packet of unattended.sourceforge.net ROOT ACCESS TO MY SERVER: Go to your console and type: telnet pxeshit.dyndns.org User: guest pass: test Type two times cd.. and you are in the root folder (hopefully somebody finds the problem) and FTP Access: Go to your console and type: ftp pxeshit.dyndns.org User: guest Pass: test Thanks in advance - Original Message - From: To: "Radu - Eosif Mihailescu" Cc: Sent: Wednesday, August 05, 2009 4:12 PM Subject: Re: [Unattended] Problems with PXE and unattended-4.8 > Zitat von Radu - Eosif Mihailescu : > >> 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 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/ > > Right now I tried to boot with the unattended.sourceforge bootdisks (I > wrote the fetnd.imz to a floppy) and it worked fantastic. The only > problem is to boot this image via PXE. > > I hope somebody knows the reason. > > Thanks > > > -- > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and focus > on
Re: [Unattended] Problems with PXE and unattended-4.8
Zitat von Radu - Eosif Mihailescu : > 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 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/ Right now I tried to boot with the unattended.sourceforge bootdisks (I wrote the fetnd.imz to a floppy) and it worked fantastic. The only problem is to boot this image via PXE. I hope somebody knows the reason. Thanks -- 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
Re: [Unattended] Problems with PXE and unattended-4.8
Zitat von Radu - Eosif Mihailescu : > 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 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 knownormally 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
Re: [Unattended] Problems with PXE and unattended-4.8
I'm sorry Patrick! Some one (I thought you) ask why some one using dos boot disk. My answer was a little explanation, why this infrastructure could be used. I do not want bother you. Sincerelly Tovis > Interesting. > > But I was talking about unattended's DOS Boot disk. Not dos boot disks > in general > > Patrick > > -Original Message- > From: tovis [mailto:mailer.to...@freemail.hu] > Sent: Monday, August 03, 2009 1:51 AM > To: Patrick Benton > Cc: unattended-info@lists.sourceforge.net > Subject: Re: [Unattended] Problems with PXE and unattended-4.8 > > Hi Patrick! > > DOS boot method some times take a very good job. I'm succeed integrate > Hiren's boot disk (exclude mini XP) on my Debian deployment "system". > Unfortunately, I suspect, that the Hiren's boot disk is an illegal > collection, but highly power full tool for windows repair. > > Sincerely > Tovis > >> 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 >> >> 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, please try to switch to the Linux boot disk and >> see if it solves your problem. >> >> >> Have a nice evening everyone, >> @Dexter >> >> On 08/02/2009 10:34 PM, Patrick Benton wrote: >> >> Why are you using memdisk? Its ok at booding dos boot disks. But > doesn't >> seem to do well on CD images. This is my relevant pxelinux.cfg. >> >> label unattended >> MENU LABEL ^Unattended Windows install >> kernel unattended/bzImage >> # Add options (z_user=..., z_path=..., etc.) to this line. >> append initrd=unattended/initrd z_path=\\ntinstall\install >> >> >> in otherwords, extract out the netboot stuff. Boot the kernel and > append >> the initrd. Works great. >> >> Patrick Benton >> IT Specialist >> Commnet Wireless LLC >> >> > >> support: >> 720-733-7688 >> supp...@commnetwireless.com >> >> > >> - >> Direct: >> 720-733-5373 >> pben...@commnetwireless.com >> P Before printing this document, please think about the environment >> >> -Original Message- >> From: r...@krautmann.net [mailto:r...@krautmann.net] >> Sent: Saturday, August 01, 2009 9:40 AM >> To: unattended-info@lists.sourceforge.net >> Subject: [Unattended] Problems with PXE and unattended-4.8 >> >> Hi friends, >> >> I have a serious problem with unattended-4.8. >> >> I installed everything on my eisfair server. DHCP, DNS and TFTP are >> running. >> >> When I start one of my clients it gets successfully an IP address, and >> then the message appears >> >> "Loading unattended/memdisk..OK" >> "Loading unattended/undis3c.imz..OK" >> Ready.. >> >> And from this point
Re: [Unattended] Problems with PXE and unattended-4.8
Interesting. But I was talking about unattended's DOS Boot disk. Not dos boot disks in general Patrick -Original Message- From: tovis [mailto:mailer.to...@freemail.hu] Sent: Monday, August 03, 2009 1:51 AM To: Patrick Benton Cc: unattended-info@lists.sourceforge.net Subject: Re: [Unattended] Problems with PXE and unattended-4.8 Hi Patrick! DOS boot method some times take a very good job. I'm succeed integrate Hiren's boot disk (exclude mini XP) on my Debian deployment "system". Unfortunately, I suspect, that the Hiren's boot disk is an illegal collection, but highly power full tool for windows repair. Sincerely Tovis > 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 > > 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, please try to switch to the Linux boot disk and > see if it solves your problem. > > > Have a nice evening everyone, > @Dexter > > On 08/02/2009 10:34 PM, Patrick Benton wrote: > > Why are you using memdisk? Its ok at booding dos boot disks. But doesn't > seem to do well on CD images. This is my relevant pxelinux.cfg. > > label unattended > MENU LABEL ^Unattended Windows install > kernel unattended/bzImage > # Add options (z_user=..., z_path=..., etc.) to this line. > append initrd=unattended/initrd z_path=\\ntinstall\install > > > in otherwords, extract out the netboot stuff. Boot the kernel and append > the initrd. Works great. > > Patrick Benton > IT Specialist > Commnet Wireless LLC > > > support: > 720-733-7688 > supp...@commnetwireless.com > > > - > Direct: > 720-733-5373 > pben...@commnetwireless.com > P Before printing this document, please think about the environment > > -Original Message- > From: r...@krautmann.net [mailto:r...@krautmann.net] > Sent: Saturday, August 01, 2009 9:40 AM > To: unattended-info@lists.sourceforge.net > Subject: [Unattended] Problems with PXE and unattended-4.8 > > Hi friends, > > I have a serious problem with unattended-4.8. > > I installed everything on my eisfair server. DHCP, DNS and TFTP are > running. > > When I start one of my clients it gets successfully an IP address, and > then the message appears > > "Loading unattended/memdisk..OK" > "Loading unattended/undis3c.imz..OK" > Ready.. > > And from this point nothing happens anymore. > > When I try take different memdisk version I have either the same > result or it reboots after the message "Ready". > > I hope somebody could help me, because I had already running a very > stabil unattended-4.7 version...and now I thought I make it better > (F*** Never change a running system :) > > (But I tried 4.7 also with the same result) > > Thanks for you help > > > > > > > -- > @Dexter > <mailto: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/ &g
Re: [Unattended] Problems with PXE and unattended-4.8
Hi Patrick! DOS boot method some times take a very good job. I'm succeed integrate Hiren's boot disk (exclude mini XP) on my Debian deployment "system". Unfortunately, I suspect, that the Hiren's boot disk is an illegal collection, but highly power full tool for windows repair. Sincerely Tovis > 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 > > 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, please try to switch to the Linux boot disk and > see if it solves your problem. > > > Have a nice evening everyone, > @Dexter > > On 08/02/2009 10:34 PM, Patrick Benton wrote: > > Why are you using memdisk? Its ok at booding dos boot disks. But doesn't > seem to do well on CD images. This is my relevant pxelinux.cfg. > > label unattended > MENU LABEL ^Unattended Windows install > kernel unattended/bzImage > # Add options (z_user=..., z_path=..., etc.) to this line. > append initrd=unattended/initrd z_path=\\ntinstall\install > > > in otherwords, extract out the netboot stuff. Boot the kernel and append > the initrd. Works great. > > Patrick Benton > IT Specialist > Commnet Wireless LLC > > > support: > 720-733-7688 > supp...@commnetwireless.com > > > - > Direct: > 720-733-5373 > pben...@commnetwireless.com > P Before printing this document, please think about the environment > > -Original Message- > From: r...@krautmann.net [mailto:r...@krautmann.net] > Sent: Saturday, August 01, 2009 9:40 AM > To: unattended-info@lists.sourceforge.net > Subject: [Unattended] Problems with PXE and unattended-4.8 > > Hi friends, > > I have a serious problem with unattended-4.8. > > I installed everything on my eisfair server. DHCP, DNS and TFTP are > running. > > When I start one of my clients it gets successfully an IP address, and > then the message appears > > "Loading unattended/memdisk..OK" > "Loading unattended/undis3c.imz..OK" > Ready.. > > And from this point nothing happens anymore. > > When I try take different memdisk version I have either the same > result or it reboots after the message "Ready". > > I hope somebody could help me, because I had already running a very > stabil unattended-4.7 version...and now I thought I make it better > (F*** Never change a running system :) > > (But I tried 4.7 also with the same result) > > Thanks for you help > > > > > > > -- > @Dexter > <mailto: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/ > -- > 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___
Re: [Unattended] Problems with PXE and unattended-4.8
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 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/ smime.p7s Description: S/MIME Cryptographic Signature -- 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
Re: [Unattended] Problems with PXE and unattended-4.8
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 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, please try to switch to the Linux boot disk and see if it solves your problem. Have a nice evening everyone, @Dexter On 08/02/2009 10:34 PM, Patrick Benton wrote: Why are you using memdisk? Its ok at booding dos boot disks. But doesn't seem to do well on CD images. This is my relevant pxelinux.cfg. label unattended MENU LABEL ^Unattended Windows install kernel unattended/bzImage # Add options (z_user=..., z_path=..., etc.) to this line. append initrd=unattended/initrd z_path=\\ntinstall\install in otherwords, extract out the netboot stuff. Boot the kernel and append the initrd. Works great. Patrick Benton IT Specialist Commnet Wireless LLC support: 720-733-7688 supp...@commnetwireless.com - Direct: 720-733-5373 pben...@commnetwireless.com P Before printing this document, please think about the environment -Original Message- From: r...@krautmann.net [mailto:r...@krautmann.net] Sent: Saturday, August 01, 2009 9:40 AM To: unattended-info@lists.sourceforge.net Subject: [Unattended] Problems with PXE and unattended-4.8 Hi friends, I have a serious problem with unattended-4.8. I installed everything on my eisfair server. DHCP, DNS and TFTP are running. When I start one of my clients it gets successfully an IP address, and then the message appears "Loading unattended/memdisk..OK" "Loading unattended/undis3c.imz..OK" Ready.. And from this point nothing happens anymore. When I try take different memdisk version I have either the same result or it reboots after the message "Ready". I hope somebody could help me, because I had already running a very stabil unattended-4.7 version...and now I thought I make it better (F*** Never change a running system :) (But I tried 4.7 also with the same result) Thanks for you help -- @Dexter <mailto: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/ -- 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
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, please try to switch to the Linux boot disk and see if it solves your problem. Have a nice evening everyone, @Dexter On 08/02/2009 10:34 PM, Patrick Benton wrote: Why are you using memdisk? Its ok at booding dos boot disks. But doesn't seem to do well on CD images. This is my relevant pxelinux.cfg. label unattended MENU LABEL ^Unattended Windows install kernel unattended/bzImage # Add options (z_user=..., z_path=..., etc.) to this line. append initrd=unattended/initrd z_path=\\ntinstall\install in otherwords, extract out the netboot stuff. Boot the kernel and append the initrd. Works great. Patrick Benton IT Specialist Commnet Wireless LLC support: 720-733-7688 supp...@commnetwireless.com - Direct: 720-733-5373 pben...@commnetwireless.com P Before printing this document, please think about the environment -Original Message- From: r...@krautmann.net [mailto:r...@krautmann.net] Sent: Saturday, August 01, 2009 9:40 AM To: unattended-info@lists.sourceforge.net Subject: [Unattended] Problems with PXE and unattended-4.8 Hi friends, I have a serious problem with unattended-4.8. I installed everything on my eisfair server. DHCP, DNS and TFTP are running. When I start one of my clients it gets successfully an IP address, and then the message appears "Loading unattended/memdisk..OK" "Loading unattended/undis3c.imz..OK" Ready.. And from this point nothing happens anymore. When I try take different memdisk version I have either the same result or it reboots after the message "Ready". I hope somebody could help me, because I had already running a very stabil unattended-4.7 version...and now I thought I make it better (F*** Never change a running system :) (But I tried 4.7 also with the same result) Thanks for you help -- @Dexter 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/ smime.p7s Description: S/MIME Cryptographic Signature -- 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
Re: [Unattended] Problems with PXE and unattended-4.8
Why are you using memdisk? Its ok at booding dos boot disks. But doesn't seem to do well on CD images. This is my relevant pxelinux.cfg. label unattended MENU LABEL ^Unattended Windows install kernel unattended/bzImage # Add options (z_user=..., z_path=..., etc.) to this line. append initrd=unattended/initrd z_path=\\ntinstall\install in otherwords, extract out the netboot stuff. Boot the kernel and append the initrd. Works great. Patrick Benton IT Specialist Commnet Wireless LLC support: 720-733-7688 supp...@commnetwireless.com - Direct: 720-733-5373 pben...@commnetwireless.com P Before printing this document, please think about the environment -Original Message- From: r...@krautmann.net [mailto:r...@krautmann.net] Sent: Saturday, August 01, 2009 9:40 AM To: unattended-info@lists.sourceforge.net Subject: [Unattended] Problems with PXE and unattended-4.8 Hi friends, I have a serious problem with unattended-4.8. I installed everything on my eisfair server. DHCP, DNS and TFTP are running. When I start one of my clients it gets successfully an IP address, and then the message appears "Loading unattended/memdisk..OK" "Loading unattended/undis3c.imz..OK" Ready.. And from this point nothing happens anymore. When I try take different memdisk version I have either the same result or it reboots after the message "Ready". I hope somebody could help me, because I had already running a very stabil unattended-4.7 version...and now I thought I make it better (F*** Never change a running system :) (But I tried 4.7 also with the same result) Thanks for you help -- 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 -- 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
