search for: d865gbflk

Displaying 8 results from an estimated 8 matches for "d865gbflk".

2017 Mar 24
0
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
CC:ing syslinux. Thanks for testing David. On Thu, Mar 23, 2017 at 05:23:51PM -0700, David Christensen wrote: > Trying isohdpfd.bin: ... > Boot it in D865GBFLK Pentium 4 3.4E GHz -- I see a screenful of information, > with "Key?" at the bottom (see attached picture IMG_1578-r.JPG). > > > When I press a key, I see the following message at the bottom and the > computer stops: > > ISOLINUX 6.03 20150819 CHDDisolinux: Image c...
2017 Mar 18
4
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
syslinux at zytor.com: I have two older computers with Intel D865GBFLK motherboards (~2003) and Pentium 4 HT CPU's. They both have the latest available BIOS installed. I would like to put Debian on them. I have downloaded: http://cdimage.debian.org/debian-cd/current/i386/iso-cd/debian-8.7.1-i386-xfce-CD-1.iso When I put debian-8.7.1-i386-xfce-CD-1.iso on...
2017 Mar 23
6
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
Hi, Geert Stappers wrote: > Contact David off-list, he did unsubscribe. Can you tell when he unsubscribed (i.e. which of the messages he got as last one) ? > Martin posted elsewhere in this thread "Thomas, you found the bug" > and provided a patch. Open question is whether the fix helps with David's BIOS. The newest answer from Martin indicates that a failure to read
2017 Mar 18
0
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
> syslinux at zytor.com: > > I have two older computers with Intel D865GBFLK motherboards (~2003) > and Pentium 4 HT CPU's. They both have the latest available BIOS > installed. I would like to put Debian on them. > > > I have downloaded: > > > http://cdimage.debian.org/debian-cd/current/i386/iso-cd/debian-8.7.1-i386-xfce-CD-1.iso > &g...
2017 Mar 19
2
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
...Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x5f07ed52 Device Boot Start End Sectors Size Id Type /dev/sdb1 * 2048 7591935 7589888 3.6G e W95 FAT16 (LBA) When I undock the HDD from my D865GBFLK Pentium 4 3.4E GHz computer and boot the USB drive, I see: MBR SYSLINUX 6.03 CHS 20150820 Copyright (C) 1994-2014 H. Peter Anvin et al Loading vmlinuz... After a few seconds, I see: [ 0.599372] CPU: 0 PID: 1 Comm: swapper Not tainted 3.16.0-4-586 #1 Debian3.216.39-1 [ 0.599429] Hardwar...
2017 Mar 21
0
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
...timal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x59f54072 Device Boot Start End Sectors Size Id Type /dev/sdb1 * 0 1325055 1325056 647M 0 Empty /dev/sdb2 8524 9131 608 304K ef EFI (FAT-12/16/32) Boot the USB flash drive in computer with Intel D865GBFLK motherboard and Intel Pentium 4 3.4E GHz processor: C 00000000000000000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000 00000000000000000000000000000000 000000000000...
2017 Mar 21
2
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
Hi, i have uploaded a little gz compressed tarball http://scdbackup.webframe.org/block_seq.tgz containing -rwxr-xr-x thomas/thomas 4552 2017-03-21 09:23 block_seq -rw-r--r-- thomas/thomas 315 2017-03-21 09:22 block_seq.c To be unpacked in a suitable directory by tar xvzf block_seq.tgz The binary "block_seq" was compiled on Debian Jessie. If it does not run, do cc -o
2017 Mar 19
3
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
On 03/18/2017 03:02 PM, Thomas Schmitt via Syslinux wrote: > Hi, > > David Christensen wrote: >> I use this USB flash drive for bootable installer images; I do not >> attempt to mount it. I don't know that I could, even if I wanted to: > > mkdir /mnt/iso > mount /dev/sdc /mnt/iso > > or, because partition 1 starts at block 0, you may mount it too >