similar to: PXE booting 2.88MB floppy

Doing a lot of RTFM lately about PXE. I have done xCAT builds but want to take the voodo out of the process so I can control and understand the whole system. I am new to PXE technology and so consider me ignorant. The current server is a MS RIS server and I am attempting to migrate our facility to use Linux / PXE instead. First stage: take existing DOS bootnet floppy and convert to boot from

Hi, I can access our server with \\10.0.0.25 \\lampadas \\lampadas.stjamesthegreat.org All three ways will show me a list of shares. The first two will allow me to access the shares but the last fully qualified domain name results in "\\lampadas.stjamesthegreat.org\WPKG is not accessible. You might not have permission to use this network resource. Contact the administrator of this

This patch builds a floppy image with contains HDT, so users of GRUB or GRUB4DOS can use HDT too, without installing Syslinux. When you compile Syslinux, this floppy image isn't build automatically. To build it, runthe following from the extracted Syslinux source: $ cd ./com32/hdt $ make hdt.img As suggested by Pierre-Alexandre Meyer, all extra files required for building the floppy

Hi, I'm trying to add an alternative UPN suffix. According to the guides/instructions I should be able to open Active Directory Domains and Trust then right click the top line (Active Directory Domains and Trusts) select Properties and then make changes. I just get "No properties are available on this object" I thought everything was working correctly. I can add a

Hi, Has anyone been able to sync passwords from Samba Version 4.3.11 to Office365 ? I've set up a VM running MS Server 2012 and joined it to the Samba AD domain and installed the Azure AD Sync program. User accounts are being synced ok put passwords don't seem to be going up ? When I follow the troubleshooter guide and check status of the password sync settings in powershell it

Hello list, My set up is almost complete in booting DOS through PXELinux, but I need to create a DOS boot image from (2 )DOS floppies. I've search the archives and google but didn't find any relavant info... My current set up now works with the standard setup (with one DOS floppy): kernel: memdisk append: initrd=floppy.img ramdisk=10000 My goal to is create a floppy.img from 2 DOS

I would like to be able to create a 2.88MB bootable floppy image to hold the kernel and initrd -- will be used for automated install. In various newsgroups there have been many posting attempting to describe how to achieve this, but none of them is complete. Can syslinux be used to achieve this? What about memdisk? Thank you in advance. Fet

Hi there! After reading the last posting about creating a boot disk as non-root, I have a question of my own: Does anyone know a way to produce a floppy/harddisk image able to boot a DOS environment (without using windows, vmware or other tools of that kind)? Is it perhaps even possible to create larger disk images (>2.88MB)? It's no problem to get an image with a DOS filesystem, but

Hi, Hope you don't mind, would like to check that whether could the 2.88MB Floppy drive to read a 1.44MB Floppy Disk ? Know any company still producing the 2.88MB Floppy Disks ? Many Thanks. and have a wonderful day. Best Regards, Chew, Siak Koon (Mr) Assistant IS Manager Expeditors (Malaysia) - Penang Tel : 604-6307007 Fax : 604-6428441 Mobile : 6012-474 6933 eMail :

I hope I've understand that all, somebody wants to create a floppy-image larger than 2.88MB an use it with memdisk? I have modified a tool from Bart Lagerweij (Big thanks!) and can create Floppy-Images with 5760kB and 8100kB, and boot them with ISOLINUX and MEMDISK (or also with a modified DISKEM1X.BIN), is this what you mean? These tools must run under windows, but booting no problem.

Hello All: I've recently had to provision some RHEL and CentOS VMWare instances. There was no network connectivity so I had to use a kickstart floppy and DVD iso rather than installing from our repository. To create the floppy I used the following: As root: dd if=/dev/zero of=floppy.flp bs=1k count=360 mkfs.vfat floppy.flp mount -o loop floppy.flp /mnt/floppy cp base_kickstart.ks

Hi folks, I hit the syslinux homepage for the first time in a while. The stuff just works, so there's no reason to come to the website, eh? :) Anyway, the first line is "The SYSLINUX Project covers lightweight bootloaders for floppy media (SYSLINUX)", and I think that this needs to be expanded a bit. I use SYSLINUX on CompactFlash, and it works great because together with

Fellow syslinux fans, I'm using syslinux on a boot floppy (I'll call this syslinux A) to invoke an etherboot image (zlilo style) which invokes a tagged NBI image from my DHCP/TFTP server. The tagged NBI image is created using mknbi-dos and also uses syslinux (I'll call this syslinux B), a linux kernel and an initrd file. It works perfectly if syslinux A has a basic .CFG, e.g.:

On 07/15/2014 06:57 PM, Ady wrote: > > Finally, when using MEMDISK to boot floppy images, these images > should not use partial "cylinders". In other words, use exact CHS > values for floppy images, instead of building the images by means of > the desired megabytes size. Then use the selected CHS values as > parameters for MEMDISK. > If you have a proper set

I have periodically been trying to get memdisk to boot images larger than your average 1.44Mb floppy and have always been unsuccessful. I cannot boot anything greater than 1.44Mb. The systems I'm attempting to do this with are not too old but they are not recent either. One is a Asus P5A and the other is a Intel SE440BX both with the most recent bios firmware patches available applied. If

Hi all, I love syslinux!! It works great. Problem. GHost 8.x and higher... With ghost 7.5 and earlier I was able to boot floppy images from my tftp server. But as you all know Ghost 8.x and higher had a bloated ghost.exe that does not fit on a single 1.44mb floopy image file. Has any one had any luck in getting ghost 8.x and higher to work with syslinux and memdisk? I have tried to create over

>that image under B: or X: or whatever. This will allow us to cross the >size limit of 2.88MB floppies. Ofcourse when I say "mount" I dont expect >memdisk to mount it, just that set things up so that DOS mounts it there. I'm using a 5MB image which emulates floppydisk. label test kernel data/memdisk append initrd=data2/test.img c=80 h=8 s=18 floppy problems are

It is now possible to build a bootable floppy image which contains HDT, with my patch applied to Erwans HDT branch: http://git.zytor.com/?p=users/erwan/hdt.git;a=commit;h=16b37fe2266c920087f88cdec94243b71218d871 Unpack the Syslinux archive and build whole Syslinux first, then cd to ./com32/hdt/ and make hdt.img $ make $ cd ./com32/hdt/ $ make hdt.img Now you have a 2.88 MB floppy image which

Hi, I was wondering what's the best standard file extension for zipped DOS disk images and ramdisks. I've been using the following standard: .zi kernels, memtest86, memdisk .igz .img.gz zipped floppy images and ramdisks I'd rather have a different extension for ramdisks, maybe .zim zipped floppy images .zrd zipped ramdisks Any ideas ? It would also be nice if syslinux

Just for the record, I want to let the list know that I succeeded in booting a modified Universal TCP/IP Network Bootdisk floppy from http://members.iinet.net.au/~bdriver/bootdisk/ I started with a Win98 Bootfloppy from http://www.tobs.uku.co.uk. Then I made a disk image from this, using dd.exe from cygwin. Then I converted this disk image from 1.44MB to 2.88MB with winimage. Then I copied