© J.C. Kessels 2009
MyDefrag Forum
June 20, 2013, 06:25:27 am
Welcome,
Guest
. Please
login
or
register
.
1 Hour
1 Day
1 Week
1 Month
Forever
Login with username, password and session length
News
:
Home
Help
Search
Login
Register
MyDefrag Forum
>
MyDefrag v4 Forum
>
Bugs and problems
>
ZONE202N, ZONE212N, ZONE222N are suspiciously small
Pages: [
1
]
« previous
next »
Print
Author
Topic: ZONE202N, ZONE212N, ZONE222N are suspiciously small (Read 736 times)
homay2
Newbie
Posts: 4
ZONE202N, ZONE212N, ZONE222N are suspiciously small
«
on:
March 09, 2011, 07:50:51 pm »
Hi,
I have trouble using the SortBy...(... SkipBlock()) combination. I'm not sure whether it's a bug, but it is suspicious.
I depicted the situation on the attached image. It shows MyDefrag being paused during this section:
SetVariable(zoneName,"Boot files")
FileSelect
ImportListFromBootOptimize() and not(FileName("*.msp"))
FileActions
IgnoreWrapAroundFragmentation(yes)
SortByImportSequence(Ascending SkipBlock(15,ZONE222N * 0.01))
AddGap(RoundUp(ZoneEnd,400MB))
FileEnd
I don't understand the values of ZONE202N,ZONE212N,ZONE222N: why are these so small, compared to the size of the zone, when there're NO (significant) unmovable files in the zone?
Could you help me with some explanation?
I would like to understand ZONE222N because I'm going to use it in SkipBlock() and AddGap(RoundUp(...)).
I also experienced strange behaviour when I used single-file zones (e.g. FileSelect FileName("avguard.tmp") FileActions ... FileEnd) (I'm sure that there are exactly 1 file named "avguard.tmp" on the volume). The ZoneSize, ZONE222N, ZoneEnd variables were sometimes (undeterministically) 0, although the size of the file is ~39M; but I did not collect evidence/picture about this phenomena yet.
As shown on the picture, I'm using MyDefrag 4.3.1, x64 version on Vista Ultimate.
Thanks in advance!
MyDefragQuestion.png
(17.53 KB, 1008x1338 - viewed 166 times.)
Logged
jeroen
Administrator
JkDefrag Hero
Posts: 7156
Re: ZONE202N, ZONE212N, ZONE222N are suspiciously small
«
Reply #1 on:
March 13, 2011, 01:40:49 am »
The ZONE variables count files that have not yet been processed. As the FileActions are being executed the values will change, will get lower and lower. When all actions have finished (just before "FileEnd") then they will be just about zero, counting only files that could not be moved (were not processed).
Tip: see the
Pause
command to have a script pause automatically at a specific point.
Logged
homay2
Newbie
Posts: 4
Re: ZONE202N, ZONE212N, ZONE222N are suspiciously small
«
Reply #2 on:
March 22, 2011, 07:49:34 pm »
Thank you for your reply, Jeroen!
This explains my second problem, too. I used a zone like this:
FileSelect FileName("avguard.tmp") FileActions
SortByName(Ascending)
AddGap(RoundUp(ZoneEnd + ZONE222N, 16MB))
FileEnd
Now I understand that this is bogus because ZONE222N will be zero after SortByName(), and won't add the gap I expect.
I suggest your reply is worth to include in the documentation, on the "Scripts - Variables" page under "Zone".
Sincerely,
homay
Logged
Pages: [
1
]
Print
« previous
next »
Jump to:
Please select a destination:
-----------------------------
MyDefrag v4 Forum
-----------------------------
=> Announcements
=> Questions and help
=> Bugs and problems
=> Requests for new features
=> Scripts, and other contributions
-----------------------------
JkDefrag v3 Forum
-----------------------------
=> Announcements
=> Questions and help
=> Bugs and problems
=> Requests for new features
=> Programming with the library
Loading...