similar to: Cluster Size discrepancy between FAT32 and NTFS

Hi, I am not an engineer or linux expert but I have been using syslinux to boot live disk filesets (extracted from iso's) residing on fat32 and NTFS volumes. In FAT32 there has been no problem going with larger cluster sizes up to the nominal maximum of 64K however, with NTFS it has not been possible to exceed the cluster size of 4096. With NTFS formatted using clusters of 8192 or larger,

On Tue, Jan 21, 2014 at 2:41 PM, mike setzer <qualityana at sbcglobal.net> wrote: > hello Gene, > > good to get your message > > I have not seen a link to reply to a particular thread, > so I am replying to you right now > hopefully the thread can be made to look right, also I double posted since my connection was lost > right during the first posting. Sorry, I

Hi, The following are my steps: 1. Insert a FAT32 format HDD into usb port of Linux PC. 2. After HDD mounted successfully, configure and start samba to share the HDD. 3. Using Map Network Drive of Windows XP to map the HDD to a windows network drive. 4.Open the mapped network drive, can see "NTFS" file system on the left details. It shows the wrong info, could anybody help me? Thanks

Hi! I use a Cyrix 200 MX CPU and a Motherboard with VIA Chipset. I have two Networkinterfaces, a Realtek and a NE2000 Clone. I donwloaded the iso's from redhat(7.3) and installed the packages inclusive samba. i turned NAT on and the box works fine until I access the SAMBA directories(FAT 32) with a win2k client. If I just use samba a little bit ..(directory browsing).. nothing happens. If I

> You might want to read Wikipedia's articles about "FAT32" and "Design of the FAT file system", Good pointer. I spent far far too long on that page figuring out how fat32 is designed. But the reserved sectors, there is the key. > reserved sectors Right! Immediately after the FSIS before the FAT.And it usually is 32 sectors for fat32. Take off the VBR and the FSIS,

Sorry for the late response. I am set to digest on this list. One of my chief complaints about mailman (besides non-searchable archives), is that you can either get every message or digest, but not "digest except for threads to which I have responded for which I want every message directly". > The command line installers have the core module and the bootloader file, all embedded

> > instead of _always_ adding "+1" (which would be > > incorrect and inefficient from the point of view of the resulting > > allocatable size). > > I carefully considered this, and I dispute the fact that this is incorrect. > (snip) > Still, I won't prevent you (or anybody else interested) to provide a > proper formula if you want. ;) >

> Hi Ady, > > On 2016.02.25 02:08, Ady via Syslinux wrote: > > There is an "extra" sector, in comparison to... what exactly? > > Sorry if I wasn't clear. I think I implied that the Large FAT32 fat size > had an extra sector compared to minfatsize, when of course I meant the > opposite (the Large FAT32 has one less sector than the minfatsize >

On Wed, Jan 3, 2018 at 2:38 AM, Avi Deitcher <avi at deitcher.net> wrote: > Gene, thanks for doing "Reply-All". I only get digest, so this keeps me in > the loop. Appreciated. > >> > which appears to be included in diskstart.inc. I will have to dig in and >> > see >> > how this all gets compiled (pointers always appreciated :-) ). >>

> When trying to installing Syslinux on a FAT32 drive formatted using > Ridgecrop's Large FAT32 formatting tool [1], the installer will bail due > to the minfatsize check, as there is an extra sector being used. This > fix addresses that. > > [1] http://www.ridgecrop.demon.co.uk/index.htm?fat32format.htm > The expression: "...as there is an extra sector being

Hi, all! I've a huge problem on my home network and I suspect it is samba to blame: Machine A: Fileserver running on FreeBSD 4.5 + Samba 2.2.4 Has 2 discs: 1 UFS partition and other is 80GB FAT32 partition Machine B: Win2K Pro, with maped discs to shares both to \\A\UFS and \\A\FAT32 Whenever I write files B -> A using samba, the files are beeing corrupted, but only on the shared FAT32

I am trying to transfer files between two OSX machines using a FAT32 formatted flash drive. I am transferring a "big" directory (7G). Basically I want to sync everyday my home and work computers for some directories. I tried many possible rsyncs (original supplied, fink 3.0.5/3.0.4 macports 3.0.5, rsync-2.6.3+hfsmode-1.2b2, 3.0.6+fileflags+crtimes) What I would really like to happen

On Sat, Jan 6, 2018 at 12:34 PM, Avi Deitcher <avi at deitcher.net> wrote: >> > Is the build process documented? Or am I just going to have to plod >> > through >> > the makefiles? >> >> I don't think so. > Oh well... >> > 1. Run installer >> > 2. Installer loads ldlinux.sys onto the filesystem (and copies >> >

Hi... I decided to delete my fat32 partition (sda1, with win2k on it). I did that with fdisk and added a linux partition, then formated it with "mkfs -t ext3 /dev/sda1" ... Everything seemed to work fine... I can even mount it with "mount -t ext3 /dev/sda1 /mnt" ... but there seem to be some fat32 rubbish left because when I do "mount /dev/sda1 /mnt" it seems to

On Mon, Jan 1, 2018 at 11:06 AM, Avi Deitcher via Syslinux <syslinux at zytor.com> wrote: > Hi Syslinuxers, > > I am trying to understand the basic load chain in fat32 and ext4. I dug > into the assembly for MBR, which is pretty straightforward: > > 1. Find boot partition (or use the pre-defined one at byte 440 for > altmbr.bin) > 2. Load the first 512-byte sector of

#1 yes, you should use -rt instead of -a as everything else in -a is incompatible with vfat. #2 timestamps will always be a problem on vfat. It has a 1 or 2 second resolution so --modify-window=2 is a common solution. However, if you live somewhere that has yearly clock changes (we call it daylight savings time) those will cause the timestamps to be off by an hour on top of the 1-2 second

On 2019-4-13 4:23, C. Masloch via Syslinux wrote: > MS-DOS 7.10 (first appearing in MSW 95 OSR2, later re-used in MSW 98 > and 98 SE) and 8.00 (MSW Me, and MSW XP DOS boot diskettes) both > support FAT32 equally well. > > MS-DOS 8.00 (without some patches that are around) only supports > booting in DOS mode from diskettes. Hard disk booting only succeeds > when directly

You don't have to change the system setting just change the TZ env variable in the terminal you run rsync in. On 01/16/2018 01:30 PM, John Long via rsync wrote: > Thanks a lot, Kevin. > > I have a new Linux box and tried to set it to UTC but I think gnome > outsmarted me... > > I'll use -rt and maybe ignore timestamps entirely rather than the > window. If I find

> You are thinking GRUB-like, among (too) many others. Heh, at least I am in good company. > A "sector" is not necessarily 512-bytes long. Fair enough, e.g. Advanced Format 4k sector disks. > The VBR, or Volume Boot Record, is not necessarily 512-bytes long. > Also, the VBR doesn't need to be restricted to the first sector of the volume alone. The "Design"

>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