similar to: seatools for DOS

Hi, I was hoping to use wine to run one of those stupid windows binaries that generate a floppy (at least IBM has a clue, and also offers the raw floppy image for dd-ing) In this case, the culprit is seagate's seatools: http://www.seagate.com/support/seatools/ I installed wine under debian unstable (Version: 0.0.20010824-1) and when I run the windows binary under wine, it runs but

Hi list, I''ve got a system with 3 WD and 3 seagate drives. Today I got an email that zpool status indicated one of the seagate drives as REMOVED. I''ve tried clearing the error but the pool becomes faulted again. Taken out the offending drive and plugged into a windows box with seatools install. Unfortunately seatools finds nothing wrong with the drive. Windows seems to see

Nice to see the venerable syslinux updated to version 3.35. I did happen to encounter an issue with the latest release though. I performed 'syslinux -f' on a 32MB USB drive and all seemed well...until I tried to boot from it. Error message and drive details below: - - - /error message: SYSLINUX 3.35 2007-01-28 EBIOS Loading Invalid or corrupt kernel image. boot: /bootable USB drive

I recently added a Seagate 400Gb SATA drive to my system, and it has been behaving strangely since I put it in. for one thing, the BIOS S.M.A.R.T. came up with a warning the last time I booted with it enabled, saying that I should backup my data and replace the disk (!). I still have not made any irreversible data transfers to this drive, and I have some time yet to take it back, but I'd

(I *really* need to learn this list is configured for replying to sender instead of the list itself..) Dinesh P. schreef: > Hi there, > I am using memdisk with pxelinux, i have created ms-dos boot disk from windows xp, but when i boot from it stops on starting.... > what is the problem can anybody tell me.. > please read Syslinux and Memdisk

I have been using the LEAF Bering firewall for a year or so. It boots with Syslinux 1.75. But Bering is too large for a 1440KB floppy, so it formats the diskette as 1680KB. Recently I found a small Compaq 2266 box to replace a larger Compaq 7170 to run the firewall. But when I try to boot the Bering diskette on the 2266 I get the following message: Loading Linux ............ Boot failed:

I have found something called: diskboot.img at: http://www.gtlib.gatech.edu/pub/centos/4/os/i386/images/ But it is 6Mb large (6411Kb) instead of 1411Kb And the rawreadwrirewin program gets an error on it when run on NT. On Win2000, it makes a diskette that fails to boot.. So really, HELP!!!! I 'just' discovered that my old bootable diskette is for Centos 3.0, and my other CDs are

Hello, I'm experiencing an issue where if I use vesamenu.c32 with PXELINUX 6.03 when network booting a virtual machine hosted on VMware ESXi 6.0, it hangs (the version message is printed and then nothing - the VM has to be powered off and back on again). This happens no matter if I choose the E1000 network interface or the VMXNET3 network interface when creating the VM. The same problem

hi guys I have rather a large set of Seagate's SAS ST32000444SS, over a hundred - experience I'm having from those in conjunction with their tech support is abysmal. I'm trying to update firmware of these drives and nothing works, including tech support. ... and I cannot help but wonder - is just me who is so unlucky and getting very, very poor support(taking naturally only of

Hello, Thanks very much for your suggestions. I have double checked that all .c32 files are from the same version of syslinux. What I don't know - I only put those .c32 files I have in there on the basis of trial and error - is what .c32 files are actually needed for menu.c32 and/or vesamenu.c32. I thought perhaps there might be a .c32 file missing that I needed to put in there (though

I'm trying to connect to aSamba 1.9.18p10 share on my HP-UX 10.20 host, using an MS-DOS boot diskette (well, actually a Windows 95 boot diskette, but relying on the DOS-style protocol stack, etc.). When I issue the same username and password that I use to connect to that share from my Windows NT client, I get an invalid password message. Two things come to mind: is the DOS client sending my

On 26/09/18 20:19, Mauricio Tavares wrote: > If ti makes you feel any better, I am not having stellar service from > WD's support. In fact, they act like they never received the HD I sent > for RMA whose tracking number says they did 10 days ago. > > On Wed, Sep 26, 2018 at 2:16 PM, lejeczek via CentOS <centos at centos.org> wrote: >> hi guys >> >> I have

Hello Chris, On Thu, 01 Feb 2018 17:00:03 +0000 Chris Murphy <lists at colorremedies.com> wrote: > You can to use efibootmgr for this. NVRAM boot entry is what changed, not > the contents of the EFI System partition. > > efibootmgr -v > > Will list all entries and Boot Order. You need to use --bootorder to make > sure the CentOS entry is first. Interesting.. thanks

I have just pushed out SYSLINUX 3.10-pre21; this fixes ISOLINUX, and adds a fix for MEMDISK -- it so happens that running ISOLINUX under Bochs triggers a bug with similar behaviour as I've seen reported on here, so I'm *hoping* this might fix the "doesn't work without harddisk" problem and perhaps the IBM/USB problem some people have been reporting. Again, I really want

Hi there, I am using memdisk with pxelinux, i have created ms-dos boot disk from windows xp, but when i boot from it stops on starting.... what is the problem can anybody tell me.. Regards, Yogesh

Hi all, Do any of you have any ideas for getting a DOS floppy to reboot to the hard drive (which may contain Windows 98 or XP or Linux or Novell etc etc)? I want to use syslinux, but it does not support the localboot option like pxelinux and isolinux do. Basically, I want to boot DOS from a floppy, run some DOS stuff, then reboot to the hard drive while leaving the floppy disk in the drive.

HPA, is it possible to add GZ support in syslinux itself? Some standalone software compresses very well, but is not compressed. Example is the Memtest86+ binary (90KB uncompressed --> 35KB gzip'd) and maybe Smart Boot Manager (gzip'd COM32 binary instead of normal COM32 binary?). I'm using both on a simple bootdisk, and all space savings are welcome. a workaround could ofcourse

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, I have recently bought a new disk (Seagate 500G, ST3500320NS). I have enabled SMART checking using the smartmontools as usual for the disk (/dev/ad6 -a -S on -s (S/../.././03|L/../../7/03) -m root). The problem is that each time the test runs I get messages like the following in /var/log/messages: Oct 26 04:54:15 35 kernel: ad6: TIMEOUT -

A few weeks back I had tried to install CentOS on my old AMD 5x6x (equiv to P75 performance) with plans to use it as my firewall and router. Because there were some problems relating to RPM compile architecture (apparently), I posted and Bryan suggested IPCop, even at peril to his life on these lists ;-) according to him. ;-) ;-) Just wanted to tell him thanks, it's worked out well. Had

Hi, is there an easy way to circumvent the SYSLINUX novice protection thing? intended users don't know about CTRL key to circumvent it. I'm trying to make a generic bootdisk for systems of 8086 - Pentium4. however the bootdisk is slow, so I'd like to use Syslinux + Memdisk to load a diskette image. then the text displayed to user will be: 1) FreeDOS bootdisk (accelerated, 386