WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Syslinux 4.05 or 4.06?  (Read 710 times)

Offline PDP-8

  • Sr. Member
  • ****
  • Posts: 469
Syslinux 4.05 or 4.06?
« on: July 09, 2019, 02:04:03 AM »
Something unusual noticed in regards to syslinux ...

Even though yes, I have to move and rename directories, and modify isolinux.cfg to be syslinux.cfg and so on, just wondering if 4.05 of syslinux is giving me fits, rather than the later 4.06 version?

Out of curiosity, I ran the Rufus logs on tinycorepure64-10.1 iso and noticed this in the iso analysis section ...

Code: [Select]
Rufus x86 v3.5.1497
Windows version: Windows 10 64-bit (Build 17763)
Syslinux versions: 4.07/2013-07-25, 6.03/2014-10-06
Grub versions: 0.4.6a, 2.02
System locale ID: 0x0409 (en-US)
Will use default UI locale 0x0409
SetLGP: Successfully set NoDriveTypeAutorun policy to 0x0000009E
Localization set to 'en-US'
Found USB 2.0 device 'SanDisk Cruzer Blade USB Device' (0781:5567)
Found card reader device 'Toshiba 032G34'
1 device found
Disk type: Removable, Disk size: 16 GB, Sector size: 512 bytes
Cylinders: 1946, Tracks per cylinder: 255, Sectors per track: 63
Partition type: GPT, NB Partitions: 1
Disk GUID: {52FB07C1-A716-424A-BB19-3E82EF56A6CB}
Max parts: 128, Start Offset: 17408, Usable = 16008575488 bytes
Partition 1:
  Type: {EBD0A0A2-B9E5-4433-87C0-68B6B72699C7}
  Name: 'Microsoft Basic Data'
  ID: {BED9F4BB-3755-4B07-86C2-47E13644FCC9}
  Size: 14.9 GB (16007544320 bytes)
  Start Sector: 2048, Attributes: 0x0000000000000000
Scanning image...
ISO analysis:
  Image is an ISO9660 image
  Will use '/boot/isolinux/isolinux.cfg' for Syslinux
  Detected Syslinux version: 4.05/0x4f92e181 (from '/boot/isolinux/isolinux.bin')
  Detected EFI bootloader(s) (from '/EFI/BOOT/efiboot.img'):
  ● 'bootx64.efi'
Disk image analysis:
  Image has an unknown Master Boot Record
  Image is a bootable disk image
ISO label: 'TinyCorePure64'
  Size: 25.4 MB (Projected)
  Note: File on disk is larger than reported ISO size by 244 KB...
  Uses: Syslinux/Isolinux v4.05
  Uses: EFI (through '/EFI/BOOT/efiboot.img')
Using image: TinyCorePure64-10.1.iso (26 MB)

Format operation started
Requesting disk access...
Will use 'D:' as volume mountpoint
Deleting partitions...
Deleting ALL partitions from disk '\\?\PhysicalDrive1':
● Partition 1 (offset: 1048576, size: 14.9 GB)
Opened \\.\PhysicalDrive1 for exclusive write access
Analyzing existing boot records...
Drive has a Zeroed Master Boot Record
Clearing MBR/PBR/GPT structures...
Erasing 128 sectors
Deleting partitions...
Partitioning (GPT)...
Closing existing volume...
Waiting for logical drive to reappear...
Formatting (FAT32)...
Using cluster size: 8192 bytes
Quick format was selected
Creating file system...
Format completed.
Writing master boot record...
Drive has a Zeroed Master Boot Record
Using Rufus protective MBR
Found volume GUID \\?\Volume{e1f98bca-a1f2-11e9-8594-d8c4971025d1}\
Successfully remounted \\?\Volume{e1f98bca-a1f2-11e9-8594-d8c4971025d1}\ on D:
Copying ISO files...
Extracting files...
Image is an ISO9660 image
This image will be extracted using Joliet extensions (if present)
Extracting: D:\EFI\BOOT\efiboot.img (1.4 MB)
Extracting: D:\EFI\BOOT\grub\fonts\unicode.pf2 (2.4 MB)
Extracting: D:\EFI\BOOT\grub\grub.cfg (586 bytes)
Extracting: D:\boot\corepure64.gz (9.9 MB)
Extracting: D:\boot\isolinux\boot.cat (2 KB)
Extracting: D:\boot\isolinux\boot.msg (1 KB)
Extracting: D:\boot\isolinux\f1 (242 bytes)
Extracting: D:\boot\isolinux\f2 (1003 bytes)
Extracting: D:\boot\isolinux\f3 (1.2 KB)
Extracting: D:\boot\isolinux\f4 (1 KB)
Extracting: D:\boot\isolinux\isolinux.bin (24 KB)
Extracting: D:\boot\isolinux\isolinux.cfg (1.5 KB)
Extracting: D:\boot\isolinux\menu.c32 (59.9 KB)
Extracting: D:\boot\vmlinuz64 (4.5 MB)
Extracting: D:\cde\copy2fs.lst (339 bytes)
Extracting: D:\cde\onboot.lst (339 bytes)
Extracting: D:\cde\optional\Xfbdev.tcz (356 KB)
Extracting: D:\cde\optional\Xfbdev.tcz.md5.txt (45 bytes)
Extracting: D:\cde\optional\Xlibs.tcz (1.1 MB)
Extracting: D:\cde\optional\Xlibs.tcz.md5.txt (44 bytes)
Extracting: D:\cde\optional\Xprogs.tcz (136 KB)
Extracting: D:\cde\optional\Xprogs.tcz.md5.txt (45 bytes)
Extracting: D:\cde\optional\aterm.tcz (64 KB)
Extracting: D:\cde\optional\aterm.tcz.md5.txt (44 bytes)
Extracting: D:\cde\optional\bzip2-lib.tcz (28 KB)
Extracting: D:\cde\optional\bzip2-lib.tcz.md5.txt (48 bytes)
Extracting: D:\cde\optional\fltk-1.3.tcz (488 KB)
Extracting: D:\cde\optional\fltk-1.3.tcz.md5.txt (47 bytes)
Extracting: D:\cde\optional\flwm.tcz (32 KB)
Extracting: D:\cde\optional\flwm.tcz.md5.txt (43 bytes)
Extracting: D:\cde\optional\freetype.tcz (404 KB)
Extracting: D:\cde\optional\freetype.tcz.md5.txt (47 bytes)
Extracting: D:\cde\optional\glib2.tcz (1.3 MB)
Extracting: D:\cde\optional\glib2.tcz.md5.txt (44 bytes)
Extracting: D:\cde\optional\graphite.tcz (80 KB)
Extracting: D:\cde\optional\graphite.tcz.md5.txt (47 bytes)
Extracting: D:\cde\optional\harfbuzz.tcz (336 KB)
Extracting: D:\cde\optional\harfbuzz.tcz.md5.txt (47 bytes)
Extracting: D:\cde\optional\imlib2-bin.tcz (40 KB)
Extracting: D:\cde\optional\imlib2-bin.tcz.md5.txt (49 bytes)
Extracting: D:\cde\optional\imlib2.tcz (216 KB)
Extracting: D:\cde\optional\imlib2.tcz.md5.txt (45 bytes)
Extracting: D:\cde\optional\libICE.tcz (40 KB)
Extracting: D:\cde\optional\libICE.tcz.md5.txt (45 bytes)
Extracting: D:\cde\optional\libSM.tcz (16 KB)
Extracting: D:\cde\optional\libSM.tcz.md5.txt (44 bytes)
Extracting: D:\cde\optional\libX11.tcz (928 KB)
Extracting: D:\cde\optional\libX11.tcz.md5.txt (45 bytes)
Extracting: D:\cde\optional\libXau.tcz (8 KB)
Extracting: D:\cde\optional\libXau.tcz.md5.txt (45 bytes)
Extracting: D:\cde\optional\libXdmcp.tcz (8 KB)
Extracting: D:\cde\optional\libXdmcp.tcz.md5.txt (47 bytes)
Extracting: D:\cde\optional\libXext.tcz (28 KB)
Extracting: D:\cde\optional\libXext.tcz.md5.txt (46 bytes)
Extracting: D:\cde\optional\libXfont.tcz (112 KB)
Extracting: D:\cde\optional\libXfont.tcz.md5.txt (47 bytes)
Extracting: D:\cde\optional\libXmu.tcz (52 KB)
Extracting: D:\cde\optional\libXmu.tcz.md5.txt (45 bytes)
Extracting: D:\cde\optional\libXt.tcz (168 KB)
Extracting: D:\cde\optional\libXt.tcz.md5.txt (44 bytes)
Extracting: D:\cde\optional\libffi.tcz (16 KB)
Extracting: D:\cde\optional\libffi.tcz.md5.txt (45 bytes)
Extracting: D:\cde\optional\libfontenc.tcz (12 KB)
Extracting: D:\cde\optional\libfontenc.tcz.md5.txt (49 bytes)
Extracting: D:\cde\optional\libjpeg-turbo.tcz (244 KB)
Extracting: D:\cde\optional\libjpeg-turbo.tcz.md5.txt (52 bytes)
Extracting: D:\cde\optional\libpng.tcz (96 KB)
Extracting: D:\cde\optional\libpng.tcz.md5.txt (45 bytes)
Extracting: D:\cde\optional\libxcb.tcz (352 KB)
Extracting: D:\cde\optional\libxcb.tcz.md5.txt (45 bytes)
Extracting: D:\cde\optional\pcre.tcz (308 KB)
Extracting: D:\cde\optional\pcre.tcz.md5.txt (43 bytes)
Extracting: D:\cde\optional\wbar.tcz (36 KB)
Extracting: D:\cde\optional\wbar.tcz.md5.txt (43 bytes)
Extracting: D:\cde\xbase.lst (340 bytes)
Extracting: D:\efi\boot\bootx64.efi (from '/EFI/BOOT/efiboot.img', 593 KB)
Created: D:\syslinux.cfg
Finalizing, please wait...

Found USB 2.0 device 'SanDisk Cruzer Blade USB Device' (0781:5567)
Found card reader device 'Toshiba 032G34'
1 device found
Disk type: Removable, Disk size: 16 GB, Sector size: 512 bytes
Cylinders: 1946, Tracks per cylinder: 255, Sectors per track: 63
Partition type: GPT, NB Partitions: 1
Disk GUID: {A602AC0A-9072-4CD3-92A5-B48D54FD91A5}
Max parts: 128, Start Offset: 17408, Usable = 16008575488 bytes
Partition 1:
  Type: {EBD0A0A2-B9E5-4433-87C0-68B6B72699C7}
  Name: 'Microsoft Basic Data'
  ID: {A6372234-B9CB-4EF5-AF77-70F039F085A8}
  Size: 14.9 GB (16007544320 bytes)
  Start Sector: 2048, Attributes: 0x0000000000000000

I'm no boot guru, just trying to figure out why this seems so hard for me, despite these AWESOME up to date usb-installer wiki

http://wiki.tinycorelinux.net/wiki:install_usb_stepbystep

Just bummed that I have some sort of stumbling block when it comes to 64-bit UEFI-ONLY usb boot drives using things other than YUMI-UEFI.



That's a UNIX book! - cool  -- Garth

Online Rich

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 6758
Re: Syslinux 4.05 or 4.06?
« Reply #1 on: July 09, 2019, 04:57:01 AM »
Hi PDP-8
... Out of curiosity, I ran the Rufus logs on tinycorepure64-10.1 iso and noticed this in the iso analysis section ...
Noticed what? There are 161 lines in that code box. You might want to be a little more specific.

Offline PDP-8

  • Sr. Member
  • ****
  • Posts: 469
Re: Syslinux 4.05 or 4.06?
« Reply #2 on: July 09, 2019, 01:22:47 PM »
Here's the relevant lines:
Code: [Select]
ISO analysis:
  Image is an ISO9660 image
  Will use '/boot/isolinux/isolinux.cfg' for Syslinux
  Detected Syslinux version: 4.05/0x4f92e181 (from '/boot/isolinux/isolinux.bin')
  Detected EFI bootloader(s) (from '/EFI/BOOT/efiboot.img'):
  ● 'bootx64.efi'

I'm just noticing that with other isos that use syslinux, when they use 4.06 or newer, I seem to have no major difficulties with UEFI-ONLY hardware.  Ie, no csm options to be seen.   TCpure64's iso seems to have been initialized with 4.05.

And this may be benign, but I don't know about the missing 244kb:

Code: [Select]
Disk image analysis:
  Image has an unknown Master Boot Record
  Image is a bootable disk image
ISO label: 'TinyCorePure64'
  Size: 25.4 MB (Projected)
  Note: File on disk is larger than reported ISO size by 244 KB...
  Uses: Syslinux/Isolinux v4.05
  Uses: EFI (through '/EFI/BOOT/efiboot.img')
Using image: TinyCorePure64-10.1.iso (26 MB)

That's a UNIX book! - cool  -- Garth