Testing MyDefrag 4.0b1

[jonib]

Hi, and congratulations on the first beta.

I like the new interface and being able to target the files is very welcome.

I don't know what should or should not work so I'll report what I'm seeing.

But first what I'm testing on: Swedish Windows XP Pro sp2, and I have another WinXP installed on another partition and tree Vista installations and a bunch of data partitions.

My first problem I get this error whenever I run MyDefrag and the program will end if I don't use any parameters.
Next problem the interface is not in English (or Swedish ).

After my quick test to defrag my C: (system) drive it looked like it did a nice job.

I have attached the log from my first run without any parameters that did not run.

jonib

[jeroen]

Thanks for testing, I appreciate it!

Yes, the default language setting at the moment is Dutch. I still have to figure out a way to select a language in the installation program.

Your logfile shows that the program crashed on a volume that is not mounted. That's an eventuality I did not test....

[WindHydra]

I think it might be the floppy drive.  I removed the physical drive but didn't uninstall it from Device Manager.  After I uninstalled it MyDefrag starts defragging C drive right away.

[jonib]

I think it might be the floppy drive.  I removed the physical drive but didn't uninstall it from Device Manager.  After I uninstalled it MyDefrag starts defragging C drive right away.

Interesting, I have my floppy disabled too, but I have not removed the floppy hardware.

jonib

[Ratte]

Press Fortsätt in the dialog. If necessarily several times. Then it continues at least with me.

Rename language.myd. Then everything is in English.

[wingnutamj]

It's trivial, but the GUI crashes at a zoom past 4 million. You can zoom in, then everything goes black and you have to go back out to 1 to see a picture again. Really cool feature though. Amazing how deep you can go.

I don't know what you're writing this program in, but you should be able to see the current country through

System.Globalization.CultureInfo.CurrentCulture ( http://msdn.microsoft.com/en-us/library/system.globalization.cultureinfo.currentculture(VS.71).aspx )  and then from there get the language. (Requires .NET framework).

Just for giggles, here's the English language file. I'm guessing it changes the actual program though? after you run the program with the new language file you can delete it and the program stays in English.

[gaspard.leon]

quick guess at the language file:

the language token at the top defines the language for the file:

Language(languagenamehere)

Then every entry after that is the English heading, followed by the translated heading
Message("Pause",
        "Pauzeer")

---

Also just loaded the .MyD files in Notepad++ and they don't look so good (looks fine in Notepad), so I'll try and report a bug there so they can interpret the unicode correctly

Cheers for the beta, looks great!

[jeroen]

Just for giggles, here's the English language file. I'm guessing it changes the actual program though? after you run the program with the new language file you can delete it and the program stays in English.

The language file does not change the actual program. It is a configuration script and is loaded every time you run MyDefrag. The messages are by default in english, deleting the Language.MyD file will simply the translations. You can also get the english messages by uncommenting the very last line in the language file (the "Language("English") line) - which is the bug that I forgot to do, and why the beta is now in Dutch. For more information see the Language and Message script commands in the manual.

[gerdb]

Also just loaded the .MyD files in Notepad++ and they don't look so good (looks fine in Notepad), so I'll try and report a bug there so they can interpret the unicode correctly

The *.MyD files are Unicode but without a Byte Order Mark (BOM). Notepad++ does not like that. Opening and saving them in Notepad will add a BOM so they will also show correct in Notepad++, but MyDefrag 4.0b1 will complain then  . See this Thread.

[jeroen]

The *.MyD files are Unicode but without a Byte Order Mark (BOM).

Yes, MyDefrag scripts are 16-bit Unicode files. I have put it on my wish list to ignore all BOM marks.

[gerdb]

I have put it on my wish list to ignore all BOM marks.

How about interpreting them? Then it wouldn't matter whether you feed ANSI, Unicode or UTF-8 into the script processor.

[jeroen]

How about interpreting them?

Yes, the grammar needs to be extended so that the script interpreter will accept BOM marks as valid syntax.

[poutnik]

When launched FastOptimize on Vista64 system partition with LastAccess active,
it seems like ignoring Lastaccess settings.

for my system, using Jkdefrag v3
when Last Access is active , spacehogs zone is about 75 % of files.
when Last Access is inactive , spacehogs zone is about 40 % of files.

Now, run Mydefrag V4b1, it seems , according to cca 40% spacehog zone,
that Mydefrag, (at least by default setting of FastOptimize script) ignores active Last access atribute.

[poutnik]

Well, replacing "all" in fileselect of "2nd zone" by LastAccess("30 days ago","")
returned default V3 behavior with active LastAccessTimeStamps.

[jeroen]

When launched FastOptimize on Vista64 system partition with LastAccess active,
it seems like ignoring Lastaccess settings.

Ah, I see that I forgot to test if NtfsDisableLastAccessUpdate is active. JkDefrag v3 would automatically ignore the last access dates if NtfsDisableLastAccessUpdate was active. I will add it to MyDefrag v4, so that the LastAccess() fileboolean will always return TRUE if NtfsDisableLastAccessUpdate is active.