Displaying 3 results from an estimated 3 matches for "368480".
Did you mean:
36848
2010 Aug 11
0
CEBA-2010:0612 CentOS 5 i386 dhcp Update
CentOS Errata and Bugfix Advisory 2010:0612
Upstream details at : https://rhn.redhat.com/errata/RHBA-2010-0612.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( md5sum Filename )
i386:
8d06dbd42a2740d8a7babc7496a4190e dhclient-3.0.5-23.el5_5.1.i386.rpm
1233c2b8dbb2f7649b6216b99b4665b4 dhcp-3.0.5-23.el5_5.1.i386.rpm
2017 Mar 19
3
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
...oot 2048 2017/01/16 02:09:49 install.386/
dr-xr-xr-x 1 root root 4096 2017/01/16 02:09:49 isolinux/
-r--r--r-- 1 root root 268674 2017/01/16 02:11:29 md5sum.txt
dr-xr-xr-x 1 root root 4096 2017/01/16 02:09:47 pics/
dr-xr-xr-x 1 root root 2048 2017/01/16 02:09:50 pool/
-r--r--r-- 1 root root 368480 2017/01/10 13:19:04 setup.exe
dr-xr-xr-x 1 root root 2048 2017/01/16 02:09:47 tools/
-r--r--r-- 1 root root 228 2017/01/16 02:09:47 win32-loader.ini
>> I need a debugging version of whatever program is generating the error
>> message "isolinux.bin missing or corrupt".
&...
2017 Mar 18
4
"isolinux.bin missing or corrupt" when booting USB flash drive in old PC
On 03/18/2017 01:18 AM, Ady Ady via Syslinux wrote:
> Some of the things you should / could (re)test / (re)try:
>
> _ Verify the md5sum of the ISO image.
SHA256 verified for downloaded image and for contents of USB flash drive
(see below).
> _ Is this particular USB device _still_ capable of booting newer
> computers?
Yes.
> What happens if you would try _again_ to boot a