Jump to content











Photo
- - - - -

Smallest Win10PE x64 with Wow64 wanted


  • Please log in to reply
44 replies to this topic

#26 alacran

alacran

    Silver Member

  • .script developer
  • 957 posts
  •  
    Mexico

Posted 20 March 2019 - 11:29 AM

Thanks! It made a smaller boot.wim (410MB), but when I run my SWITCH_E2B.exe app I get a FLTLIB.dll error. Any ideas on how to fix it?

 

Usually it is a lack of some dependency, once you know what you need to add to your build (see my picture), you may edit chrispe-test\Projects\Tools\wimlib.file.lists\  file.and.dependencies.txt (For 64 bit dependencies) or syswow.files.10.txt (for 32 bit dependencies on Win10 PEs) or both, depending of your needs, just adding at the end of the list your dependencies, using same syntax for path, and make a new build (preferable) or try the Post config Advanced Options.

 

Attached picture of FLTLIB.dll instances on my 10 x64 Pro 1809, but you better check in your own OS version.

 

alacran

Attached Files



#27 erwan.l

erwan.l

    Platinum Member

  • Developer
  • 2664 posts
  • Location:Nantes - France
  •  
    France

Posted 20 March 2019 - 12:05 PM

@erwan
perhaps ...
the script in post#20 was for myfragmenter.exe !!! not for getFileExtents.exe !!!

myfragmenter.exe -i "%File%"
line 1-->>>Extent 1: Lcn=495625, Vcn=0, NextVcn=2
line 2-->>>Extent 2: Lcn=28135076, Vcn=2, NextVcn=4

read in the script :
Set clusterSize=8
...
FOR /F "tokens=2,4,6,8,9 delims=:=, " %%A IN ('myfragmenter.exe -i "%File%" ^| FIND "="') DO (
-->>> token1 = Extent
-->>> token2 = 1
-->>> token3 = Lcn           Logical Cluster number for the file ?
-->>> token4 = 495625
-->>> token5 = Vcn           Virtual Cluster number for the volume ( on the media ) ?
-->>> token6 = 0
-->>> token7 = NextVcn   next (or last !) Virtual Cluster number of an extend ?
-->>> token8 = 2
-->>> token9 =
CALL :convert_LBA %%A %%B %%C %%D
%%A = 1
%%B = 495625
%%C = 0
%%D = 2
-->>> CALL :convert_LBA %%A %%B %%C %%D
...
:convert_LBA
SET /A Sectors=%clusterSize%*(%4-%3)
-->>> SET /A Sectors= 8*(2-0) =16

 

The below is indeed what I cannot "translate".

SET /A Sectors=%clusterSize%*(%4-%3)
-->>> SET /A Sectors= 8*(2-0) =16

Clustersize (in sectors) I get it.

But what are %4 and %3 variables? with a value of 2 and 0?

 

In the below, sectors cannot be a sector offset on my partition nor can it be a sector offset on my disk so I am puzzled :)

I clearly understand what is 1f2aef8 (physical sector offset to get to my file).

If I remove my partition offset to this LBA number (1f2aef8), I effectively get the logical sector offset of my file.

But what is this 310 sectors number?

getFileExtentsX64.exe c:\bootmgr
File offset 0 LBA: 1f2aef8 Sectors: 310


#28 erwan.l

erwan.l

    Platinum Member

  • Developer
  • 2664 posts
  • Location:Nantes - France
  •  
    France

Posted 20 March 2019 - 12:08 PM

Usually it is a lack of some dependency, once you know what you need to add to your build (see my picture), you may edit chrispe-test\Projects\Tools\wimlib.file.lists\  file.and.dependencies.txt (For 64 bit dependencies) or syswow.files.10.txt (for 32 bit dependencies on Win10 PEs) or both, depending of your needs, just adding at the end of the list your dependencies, using same syntax for path, and make a new build (preferable) or try the Post config Advanced Options.

 

Attached picture of FLTLIB.dll instances on my 10 x64 Pro 1809, but you better check in your own OS version.

 

alacran

 

Beware that it is not only about adding the correct files.

As we are dealing with activex, it is also about creating proper registry entries for these activex (ocx and/or dll).



#29 alacran

alacran

    Silver Member

  • .script developer
  • 957 posts
  •  
    Mexico

Posted 20 March 2019 - 12:45 PM

@steve6375

 

I didn't see your Edit untill now.

 

P.S. How can I make the SWITCH_E2B.exe app auto-start when WinPE Desktop is reached? Without Explorer, I can't seem to get it to launch?

 

Locate and edit winpeshl.ini to your needs, after successfully completing a build edit the file \ChrisPE.Files\ROOT\Windows\System32\winpeshl.ini, usually its only content is:

 

[LaunchApps]
%SYSTEMDRIVE%\Programs\User.Added.Files\WinXShell_x64\winxshell.exe -winpe

 

Add your program at the end in a new line.
 

alacran



#30 steve6375

steve6375

    Platinum Member

  • Developer
  • 6943 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 20 March 2019 - 12:49 PM

I worked around the FLTLIB.dll issue by extracting the files from the self-extracting SWITCH_E2B.exe first.

Now the basic vb exe file runs - BUT it seems to fail when redirecting output. This did not happen on the other WinBuilder projects.

Not sure why! SWITCH_E2B copies the getfileextents.exe to X:\Windows\TEMP and then the VB6 code runs it as a shell command using

cmd /c X:\Windows\TEMP\getfileextents "C:\_ISO\myfile.imgPTN" > X:\WINDOWS\TEMP\GF.txt

A temporary file seems to be made (~sdssfsdfw-morecharactershere-eoweff.tmp)  but not the actual GF.txt file (in this case).

But running the same command from the command line works OK... weird!



#31 alacran

alacran

    Silver Member

  • .script developer
  • 957 posts
  •  
    Mexico

Posted 20 March 2019 - 12:59 PM

@ steve6375

 

You could make a compressed portable and extract all your program files/folders and requirements including dependencies (it usually works this way too) to X:Temp, X:windows\Temp etc.

 

See this post: http://reboot.pro/to...pe/#entry202768

 

alacran



#32 erwan.l

erwan.l

    Platinum Member

  • Developer
  • 2664 posts
  • Location:Nantes - France
  •  
    France

Posted 20 March 2019 - 01:04 PM

Out of curiosity, any reason why you need the physical offset of the file?

I guess you are later dumping this partition image onto a partition.

Why not simply use createfile to get a handle of the file and then use writefile to write block by block to your partition?

 

Reading directly from disk, you need to ensure your file is contiguous (or map each cluster) which is risky/overdone.

Using a plain createfile/writefile will take away the disk/cluster complexity from your code.

 

If I get it right, switch_e2b does 2 things ?

-write a partition image to a partition

-switch partition 1 and 2 (for usb disks) 

 

hl0Y6C5.png



#33 noel

noel

    Frequent Member

  • Advanced user
  • 111 posts
  • Location:nantes
  •  
    France

Posted 20 March 2019 - 01:09 PM

 

then the VB6 code runs it as a shell command using...But running the same command from the command line works OK

You make your test with CMD.EXE from 32 or 64 bits ?

Have you really try from …\syswow64\cmd.exe ? 

Can you send or share a procmon 's trace, please.



#34 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14777 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 20 March 2019 - 01:09 PM

@erwan.l
The good thing of batch it that it is (relatively) easy to display (adding an echo command) what happens.
example output of myfragi.cmd (as posted) for a contiguous file:

C:\>myfragi.cmd C:\appoggio\Alcor\LoadDriver.exe
Ext:      Lcn:      LBAstart:  Sects: File:
   1    32014747    256118039      40 C:\appoggio\Alcor\LoadDriver.exe

The output of myfragi.cmd after having inserted a few clarifying lines

C:\>myfragi.cmd C:\appoggio\Alcor\LoadDriver.exe
Ext:      Lcn:      LBAstart:  Sects: File:
#1 is 1
#2 is 32014747
#3 is 0
#4 is 5
SET /A Sectors=8*(5-0)
   1    32014747    256118039      40 C:\appoggio\Alcor\LoadDriver.exe

 
The inserted lines in RED:

...
SET /A LBAstart=%InitialLBA%+%2*%clusterSize%

ECHO #1 is %1
ECHO #2 is %2
ECHO #3 is %3
ECHO #4 is %4
echo SET /A Sectors=%clusterSize%*(%4-%3)
SET /A Sectors=%clusterSize%*(%4-%3)
...

Actual output for the same file of myfragmenter -i:

 

 

C:\>myfragmenter.exe -i C:\appoggio\Alcor\LoadDriver.exe
MyFragmenter v1.2, 2008 J.C. Kessels

Commandline argument '-i' accepted.

Processing: C:\appoggio\Alcor\LoadDriver.exe
Fragment list:
Extent 1: Lcn=32014747, Vcn=0, NextVcn=5
5 clusters, 1 fragments.

Finished, 1 files processed.

As hinted before, that was a half*@§§edly and quickly written on-the-fly and specific to the situation of the OP on MSFN, it is limited in size (by batch math) and specific to the NTFS filesystem, where *everything* is a cluster.

The "right" way to determine LBA from cluster number is filesystem dependent, and of course the hardcoded 63 sectors before and the cluster size of 8 sectors needs to be determined by parsing the BPB of the partition/volume at hand.

You need to get:
a. Sectors per cluster
b. Sectors before (i.e. start of the volume/partition)
c. Reserved sectors (if any)
d. size of FAT tables (if any)
e. number of FAT tables (if any)

 

LCNx as LBA: b+c+d*e+a*LCNx

Example:
a=8 (hardcoded in the batch)

b=63 (hardcoded in the batch)

c=0 (No reserved sectors in NTFS)
d=0 (No FAT table in NTFS)
e=0 (No FAT table in NTFS)

 

63+0+0*0+8*32014747=256118039

 

Other example (smallish FAT 32 volume):

E:\Appoggio>myfragmenter -i e:\appoggio\LoadDriver.exe
MyFragmenter v1.2, 2008 J.C. Kessels

Commandline argument '-i' accepted.

Processing: e:\appoggio\LoadDriver.exe
Fragment list:
  Extent 1: Lcn=59518, Vcn=0, NextVcn=20
  20 clusters, 1 fragments.

Finished, 1 files processed.

From the bootsector:

a=2

b=63

c=38

d=793

e=2

 

63+38+793*2+2*59518=120723

 

BTW (and just for the record) Steve6375 is very familiar with these calculations as RMPEPUSB actually forcefully aligns FAT data when creating bootable sticks in order to make them faster.

 

:duff:

Wonko

 

 


 



#35 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14777 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 20 March 2019 - 01:21 PM

Out of curiosity, any reason why you need the physical offset of the file?

I guess you are later dumping this partition image onto a partition.

Why not simply use createfile to get a handle of the file and then use writefile to write block by block to your partition?

No, the point is that a (Linux) .iso or partition image (contiguous on filesystem) is mapped to an empty partition table slot:

See "Iso fake partition" by cdob:

http://reboot.pro/to...brided/?p=88531

 

The (maybe slight) advantage of having myfragmenter handy is IMHO that it can also defragment the file (in case it is not contiguous), of course with some limitations, see (only seemingly OT):

http://reboot.pro/to...disk-emulation/

 

Practical example:



E:\Appoggio>MyFragmenter.exe -p 8 LoadDriver.exe
MyFragmenter v1.2, 2008 J.C. Kessels

Commandline argument '-p' accepted, parts = 8

Processing: LoadDriver.exe
File already exists.
Fragment list (before):
  Extent 1: Lcn=59518, Vcn=0, NextVcn=20
  20 clusters, 1 fragments.
Fragmenting:
  Largest gap: 59539 - 65536 (5997 clusters)
  Moving 3 clusters from offset=0 to LCN=62536
  Largest gap: 59539 - 62536 (2997 clusters)
  Moving 3 clusters from offset=3 to LCN=61036
  Largest gap: 62539 - 65536 (2997 clusters)
  Moving 3 clusters from offset=6 to LCN=64036
  Largest gap: 59539 - 61036 (1497 clusters)
  Moving 3 clusters from offset=9 to LCN=60286
  Largest gap: 61039 - 62536 (1497 clusters)
  Moving 3 clusters from offset=12 to LCN=61786
  Largest gap: 62539 - 64036 (1497 clusters)
  Moving 3 clusters from offset=15 to LCN=63286
  Largest gap: 64039 - 65536 (1497 clusters)
  Moving 3 clusters from offset=18 to LCN=64786
Fragment list (after):
  Extent 1: Lcn=62536, Vcn=0, NextVcn=3
  Extent 2: Lcn=61036, Vcn=3, NextVcn=6
  Extent 3: Lcn=64036, Vcn=6, NextVcn=9
  Extent 4: Lcn=60286, Vcn=9, NextVcn=12
  Extent 5: Lcn=61786, Vcn=12, NextVcn=15
  Extent 6: Lcn=63286, Vcn=15, NextVcn=18
  Extent 7: Lcn=64786, Vcn=18, NextVcn=20
  20 clusters, 7 fragments.

Finished, 1 files processed.


E:\Appoggio>MyFragmenter.exe -p 0 LoadDriver.exe
MyFragmenter v1.2, 2008 J.C. Kessels

Commandline argument '-p' accepted, parts = 0

Processing: LoadDriver.exe
File already exists.
Fragment list (before):
  Extent 1: Lcn=62536, Vcn=0, NextVcn=3
  Extent 2: Lcn=61036, Vcn=3, NextVcn=6
  Extent 3: Lcn=64036, Vcn=6, NextVcn=9
  Extent 4: Lcn=60286, Vcn=9, NextVcn=12
  Extent 5: Lcn=61786, Vcn=12, NextVcn=15
  Extent 6: Lcn=63286, Vcn=15, NextVcn=18
  Extent 7: Lcn=64786, Vcn=18, NextVcn=20
  20 clusters, 7 fragments.
Fragmenting:
  Largest gap: 64788 - 65536 (748 clusters)
  Moving 20 clusters from offset=0 to LCN=65152
Fragment list (after):
  Extent 1: Lcn=65152, Vcn=0, NextVcn=20
  20 clusters, 1 fragments.

Finished, 1 files processed.


E:\Appoggio>MyFragmenter.exe -i LoadDriver.exe
MyFragmenter v1.2, 2008 J.C. Kessels

Commandline argument '-i' accepted.

Processing: LoadDriver.exe
Fragment list:
  Extent 1: Lcn=65152, Vcn=0, NextVcn=20
  20 clusters, 1 fragments.

Finished, 1 files processed.

:duff:

Wonko



#36 steve6375

steve6375

    Platinum Member

  • Developer
  • 6943 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 20 March 2019 - 01:57 PM

@erwan

SWITCH_E2B checks that the .imgPTN file is contiguous. You cannot have a partition entry in a partition table that is not contiguous!

So the output of getfileextents is checked to see if the file is contiguous.

 

SWITCH_E2B then finds the LBA start address of the .imgPTN file and the size in sectors and then writes the values directly to the MBR partition table for the first entry (thus replacing the current E2B contents). It also tweaks some bytes in the PBR (reserved sectors) too.

So the actual physical start address of the file is needed.

It does more stuff too (like a second partition can be added), lock disk access, etc. and makes backups into LBA30 and LBA60.

I can send you the VB6 code if you like?



#37 erwan.l

erwan.l

    Platinum Member

  • Developer
  • 2664 posts
  • Location:Nantes - France
  •  
    France

Posted 20 March 2019 - 02:09 PM

Ah OK I get it.

 

You are actually not reading the whole file to write it back to a partition (Wrong assumption on my side to start with).

You are retrieving the physical offset of a contiguous file (a partition image) to update the partition table of a disk.

Crystal clear.

 

By looking at the VB6 code, I can eventually help you turn it into a x32/x64 application.

Either in vb.net (to allow you to take over easily afterwards) or in freepascal.

 

I have a lot of routines in CloneDisK which do about the same as of what you are describing.



#38 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14777 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 20 March 2019 - 03:43 PM

You are retrieving the physical offset of a contiguous file (a partition image) to update the partition table of a disk.

Crystal clear.

Physical offset AND size in sectors of the contiguous file, to be picky.

 

:duff:

Wonko



#39 erwan.l

erwan.l

    Platinum Member

  • Developer
  • 2664 posts
  • Location:Nantes - France
  •  
    France

Posted 20 March 2019 - 06:41 PM

Physical offset AND size in sectors of the contiguous file, to be picky.

 

:duff:

Wonko

 

Never too picky ! :)

I never had thought of doing that actually : clever ...



#40 erwan.l

erwan.l

    Platinum Member

  • Developer
  • 2664 posts
  • Location:Nantes - France
  •  
    France

Posted 20 March 2019 - 06:55 PM

@erwan.l
The good thing of batch it that it is (relatively) easy to display (adding an echo command) what happens.
example output of myfragi.cmd (as posted) for a contiguous file:

 

...

 

:duff:

Wonko

 

 

 

 

Actually my (personal) issue is that I cannot put a meaning on this "sectors" thingie.

 

What is it?

A physical sector offset? does not look like it it.

A partition sector offset? neither.

The number of sectors of this file? neither.

 

If I could put a description behind it, then i could probably understand the formula.



#41 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14777 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 20 March 2019 - 07:13 PM

Never too picky ! :)
I never had thought of doing that actually : clever ...

Naaah, you perfectly know how both are needed, you only forgot to describe that .
 
Just for the record and for the casual onlooker, a partition table entry (LBA part) has two fields:
1) Sectors Before (or Start LBA)
2) Size in sectors (or Num LBA)
 
As a matter of fact, nothing prohibits from putting in #2 a completely "wrong" number, as long as it is smaller or at the most equal to the number of sectors remaining from the Start LBA to the end sector of the device (never tried with a larger number, though).
I.e., in the case of those RMPREPUSB/EASY2BOOT sticks one could in theory get only the offset, and put as extents the difference between it and the sum of the two fields in first partition entry.
 
 
 

Actually my (personal) issue is that I cannot put a meaning on this "sectors" thingie.
 
What is it?
A physical sector offset? does not look like it it.
A partition sector offset? neither.
The number of sectors of this file? neither.
 
If I could put a description behind it, then i could probably understand the formula.

 
Let's take this output:
C:\>myfragmenter.exe -i C:\appoggio\Alcor\LoadDriver.exe
MyFragmenter v1.2, 2008 J.C. Kessels

Commandline argument '-i' accepted.

Processing: C:\appoggio\Alcor\LoadDriver.exe
Fragment list:
Extent 1: Lcn=32014747, Vcn=0, NextVcn=5
5 clusters, 1 fragments.

Finished, 1 files processed.
Lcn is (absolute) Logical (volume) cluster number.
A cluster number being a structure of the volume is absolute within the volume but not absolute with regards to the disk.
You multiply that number by cluster size and you have the relative LBA (from start of the volume).
To it you add the sectors before (or offset to the start of the volume) and you obtain the actual absolute LBA (from the beginning of disk), as seen for NTFS, where everything is a cluster, and the very first sector of the volume belongs to cluster 0, and/or adding the other items before cluster 0 for other filesystems.
Vcn is (relative to the file) Virtual cluster number.
For a contiguous file it is always (obviously) 0.
NextVcn is (relative to the file) Next Virtual cluster number, in practice it is (in case on non-contiguous files) the offset to where the next part of the file is, in case of a contiguous file, there is no such next part (you may think of it as first following cluster that is NOT part of the contiguous file), hence:
NextVcn-Vcn=number of clusters used by file, 5-0=5,  same as in the line:
5 clusters, 1 fragments
which you then multiply by the number of sectors per cluster to obtain file size in sectors, in the batch I only parse the line:
Extent 1: Lcn=32014747, Vcn=0, NextVcn=5
 
because it is easier/faster:
FOR /F "tokens=2,4,6,8,9 delims=:=, " %%A IN ('myfragmenter.exe -i "%File%" ^| FIND "="') DO (
but I could well do something like:
FOR /F "tokens=1 delims= " %%A IN ('myfragmenter.exe -i "%File%" ^| FIND "clusters,"') DO ( 
and get the 5 (number of clusters) already calculated by the program but that would mean running the program twice, or I could use FIND "," and check if a token equals "clusters", everyone would probably use a slightly different approach.
 
There may be obviously a mis-match between the actual file size (as seen in the filesystem) in bytes and the result of the above, once multiplied by sector size, just like if you have a 1025 byte file (size seen in the filesystem) it will occupy three sectors but really-really a whole cluster, 8*512=4096 bytes "on disk", but the calculation is correct for the LBA entry.
 
 
:duff:
Wonko

#42 steve6375

steve6375

    Platinum Member

  • Developer
  • 6943 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 20 March 2019 - 07:31 PM

FYI: SWITCH_E2B uses the exact sector size of the file so that the partition can be formatted and installed with or by another OS if the user so desires (or in case that he\she unintentionally formats the wrong drive!), without corrupting the other (hidden and inaccessible) files on the USB drive. e.g. Ptn1 can contain a Live Linux USB and Ptn2 can contain an 'junk' file which the OS can format and use as swap or persistence or data partition.

So each partition should exactly match the file extent.

One slight issue is that when two image files-to-partitions are 'switched-in' - some UEFI systems do not like two partitions in the wrong order (e.g. ptn1 points to LBA 200000 and ptn2 points to LBA 2048) - this means the two files must be in the correct order on the drive to UEFI-boot successfully on some systems. Of course this is not in the UEFI-spec - but hey ho!

Another issue is the some OS's (e.g. BSD-based) do not like overlapping partitions which can happen if you keep an original partition but try to map a file in that same partition as the 2nd partition.



#43 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14777 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 20 March 2019 - 08:18 PM

FYI: SWITCH_E2B uses the exact sector size of the file so that the partition can be formatted and installed with or by another OS if the user so desires (or in case that he\she unintentionally formats the wrong drive!), without corrupting the other (hidden and inaccessible) files on the USB drive. e.g. Ptn1 can contain a Live Linux USB and Ptn2 can contain an 'junk' file which the OS can format and use as swap or persistence or data partition.

That doesn't really-really matter in "normal" operation, the issue may arise only when you (IF you) copy the file mapped from the filesystem AND in some particular cases only.

 

If file X.ptn occupies cluster x in the "real" partition/volume, it occupies cluster x.

 

Let's say that the file is (being a multiple of one sector) 2048 bytes in size.

It occupies one cluster, i.e. on a "normal" NTFS filesystem 8*512=4096 bytes "on disk". 

You would map it as 4 sectors.

I would map it as 8 sectors.

 

You cannot write to its last 4 sectors from the "real" partition/volume (as that cluster is already assigned to the file) but you can write to them if these 4 sectors are included in the LBA map (as I would do).

 

So as long as you access it from the LBA map it works fine and you cannot modify it from the "real" partition/volume.

You can delete it from the "real" partition/volume just fine (because essentially you are making that cluster not used/unallocated).

 

The only issue is if you want to copy the file while accessing it from the "real" partition/volume, in which case it has to be seen what actually you did write to these last 4 (at the most 7) sectors while accessing the extent from the LBA map, in the case of FAT you would need to fill the volume up to the brim, in case of NTFS, besides needing to fill it up to the brim you would miss the backup bootsector, and BTW you might fall anyway in the "twilight zone" :w00t: :ph34r::

http://reboot.pro/to...ated-with-dsfo/

http://reboot.pro/to...-dsfo/?p=166592

 

Now if you copy this file to another volume/filesystem which has the same cluster size you lose "nothing" (as nothing relevant was written to those last few sectors), and the issue remains only if you copy the file to another volume filesystem that has a different (smaller) cluster size (if the destination volume has a larger cluster size ther should be no further issues). :dubbio:

 

 

But all in all there is no such problem, one can forget the size expressed in clusters by myfragmenter.exe and get it from the filesystem (DIR or similar) in bytes dividing by 512 (sector size) and rounding up by excess.

 

:duff:

Wonko



#44 steve6375

steve6375

    Platinum Member

  • Developer
  • 6943 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 20 March 2019 - 08:23 PM

by 'exact size of the file' - I meant - 'exact size that the file occupies on the disk' which is what SWITCH_E2B uses.



#45 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14777 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 20 March 2019 - 08:52 PM

by 'exact size of the file' - I meant - 'exact size that the file occupies on the disk' which is what SWITCH_E2B uses.

Well, then it is clusters anyway.

 

:duff:

Wonko




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users