Mydefrag does not start

[jeroen]

OK, I un-commented that line out and here is what I got:

Thanks, but that is not a "Debug(175)" logfile. Perhaps you deleted the "Debug(175)" line? You were only supposed to remove the "#" at the beginning of the line, which is called "uncommenting".

[nin28]

This whole interwebs thingy is all new to me! But seriously, I know what "un-commenting" a line is. Let me double check and make sure I did it right. Give me a minute and I'll re-post.

[nin28]

OK here is the Settings.MyD file:

# MyDefrag settings file.
#
# This script is called from the default scripts that are included with MyDefrag.
# It is intended for settings that you want to use for all scripts.


Language("English")

BatteryPower(ask)
Debug(175)
FileMoveChunkSize(0)
LowMemoryUsage(no)
OtherInstances(ask)
PreventPowerSaving(yes)
PreventScreenSaving(yes)
Slowdown(100)
WhenFinished(wait)
WindowSize(normal)


... and I still get the same debuglog:

Version: MyDefrag v4.1
Date: 2009/07/23 14:52:56
Windows version: v5.1 build 2600 S
Commandline: "C:\Program Files\MyDefrag v4.1\MyDefrag.exe"
Working Directory: C:\Program Files\MyDefrag v4.1
InstallPath = C:\Program Files\MyDefrag v4.1\
---> See the 'MyDefrag.log' file for information intended for endusers. This is the debug
---> logfile. The contents is highly technical and not documented. See the 'Debug' setting
---> or the '-d' commandline option to control the level of information in this file.
14:52:56 Analyzing the commandline.
14:52:56 Running script: Language.MyD
14:52:56 Running script: FastOptimize.MyD
14:52:56 Running script: Settings
14:52:56   Could not open handle: [5] Access is denied.

[jeroen]

Ok, you have uncommented the debug line properly. But the "Could not open handle: [5] Access is denied" error message makes no sense to me. The settings script does not open any files and the next message should be "Finished executing the script". Could you please try changing into "Debug(447)"? I wonder which script statement is exactly causing the error message.

[nin28]

Changed the debug setting and got the same debuglog results.

[jeroen]

Changed the debug setting and got the same debuglog results.

Sorry, that is not possible. If I was looking over your shoulder then I would probably see the problem in 2 seconds, but I am not, so I will have to rely on you to find the problem. All I can say is that if you have Debug(447) in your Settings.MyD file that it is totally impossible to get the same debuglogile.

[Darlis]

Just guessing: Maybe the Debug setting does not work, because the error appears before the Debug statement? Maybe you could edit the FastOptimize script and insert the Debug statement at the beginning?

And also make sure that you have edited the correct Settings.MyD file and not one for an older version of MyDefrag.

[nin28]

Thanks Darlis. I moved the Debug to the FastOptimize script and got an extended log. Here it is:

Version: MyDefrag v4.1
Date: 2009/07/23 16:03:57
Windows version: v5.1 build 2600 S
Commandline: "C:\Program Files\MyDefrag v4.1\MyDefrag.exe"  -r "C:\Program Files\MyDefrag v4.1\Scripts\FastOptimize.MyD"
Working Directory: C:\Program Files\MyDefrag v4.1\Scripts
InstallPath = C:\Program Files\MyDefrag v4.1\
---> See the 'MyDefrag.log' file for information intended for endusers. This is the debug
---> logfile. The contents is highly technical and not documented. See the 'Debug' setting
---> or the '-d' commandline option to control the level of information in this file.
16:03:57 Analyzing the commandline.
16:03:57   Commandline argument '-r' accepted, added 'C:\Program Files\MyDefrag v4.1\Scripts\FastOptimize.MyD' to the scripts.
16:03:57 Running script: Language.MyD
16:03:57 Running script: C:\Program Files\MyDefrag v4.1\Scripts\FastOptimize.MyD
16:03:57 Executing rule: <Statements> ::= <Statement> <Statements>
16:03:57   Token[0] = Rule = <Setting> ::= RunScript '(' String ')'
16:03:57   Token[1] = Rule = <Statements> ::= <Statement> <Statements>
16:03:57 Executing rule: <Setting> ::= RunScript '(' String ')'
16:03:57   Token[0] = Symbol('RunScript')
16:03:57   Token[1] = Symbol('(')
16:03:57   Token[2] = Symbol('String')
16:03:57   Token[3] = Symbol(')')
16:03:57 Running script: Settings
16:03:57   Locating file: Settings
16:03:57     Looking in the directory of the main script: Settings
16:03:57     Looking in the directory of the executable: C:\Program Files\MyDefrag v4.1\Settings
16:03:57     Read key 'SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\MyDefrag_is1\InstallLocation' from registry: 'C:\Program Files\MyDefrag v4.1\'
16:03:57     Looking in the installation directory: C:\Program Files\MyDefrag v4.1\Settings
16:03:57     Looking in %ProgramFiles%: C:\Program Files\MyDefrag v4.1\Settings
16:03:57     Looking in %ProgramW6432%: %ProgramW6432%\MyDefrag v4.1\Settings
16:03:57     Looking in %ProgramFiles(x86)%: %ProgramFiles(x86)%\MyDefrag v4.1\Settings
16:03:57     Looking in the PATH for: Settings
16:03:57     Found: C:\WINDOWS\system32\Settings
16:03:57   Loading file into memory: C:\WINDOWS\system32\Settings
16:03:57   Could not open handle: [5] Access is denied.
16:03:57   Stopping....
16:03:57   Finished executing the script.
16:04:00   Resetting ScreenSaverTimeout to 300
16:04:00   Resetting PowerOffTimeout to 120

It looks like the software is having trouble opening up the Settings.MyD file. I created a "settings" directory in the "MyDefrag" directory and moved the Settings.MyD into it. I also gave Everyone full rights to the settings directory and file. This is the logfile I got:

Version: MyDefrag v4.1
Date: 2009/07/23 16:22:01
Windows version: v5.1 build 2600 S
Commandline: "C:\Program Files\MyDefrag v4.1\MyDefrag.exe"  -r "C:\Program Files\MyDefrag v4.1\Scripts\FastOptimize.MyD"
Working Directory: C:\Program Files\MyDefrag v4.1\Scripts
InstallPath = C:\Program Files\MyDefrag v4.1\
---> See the 'MyDefrag.log' file for information intended for endusers. This is the debug
---> logfile. The contents is highly technical and not documented. See the 'Debug' setting
---> or the '-d' commandline option to control the level of information in this file.
16:22:01 Analyzing the commandline.
16:22:01   Commandline argument '-r' accepted, added 'C:\Program Files\MyDefrag v4.1\Scripts\FastOptimize.MyD' to the scripts.
16:22:01 Running script: Language.MyD
16:22:01 Running script: C:\Program Files\MyDefrag v4.1\Scripts\FastOptimize.MyD
16:22:01 Executing rule: <Statements> ::= <Statement> <Statements>
16:22:01   Token[0] = Rule = <Setting> ::= RunScript '(' String ')'
16:22:01   Token[1] = Rule = <Statements> ::= <Statement> <Statements>
16:22:01 Executing rule: <Setting> ::= RunScript '(' String ')'
16:22:01   Token[0] = Symbol('RunScript')
16:22:01   Token[1] = Symbol('(')
16:22:01   Token[2] = Symbol('String')
16:22:01   Token[3] = Symbol(')')
16:22:01 Running script: Settings
16:22:01   Locating file: Settings
16:22:01     Looking in the directory of the main script: Settings
16:22:01     Looking in the directory of the executable: C:\Program Files\MyDefrag v4.1\Settings
16:22:01     Found: C:\Program Files\MyDefrag v4.1\Settings
16:22:01   Loading file into memory: C:\Program Files\MyDefrag v4.1\Settings
16:22:01   Could not open handle: [5] Access is denied.
16:22:01   Stopping....
16:22:01   Finished executing the script.
16:22:07   Resetting ScreenSaverTimeout to 300
16:22:07   Resetting PowerOffTimeout to 120

Thanks.

[Darlis]

I think "Looking in the installation directory: C:\Program Files\MyDefrag v4.1\Settings" means that MyDefrag tries to find the file Settings(.MyD) and is not looking for the folder Settings. Try moving the Settings file to the executable path.

[nin28]

No luck there either. I had better success with creating the a "Setttings" directory in the MyDefrag directory and moving the Settings.MyD to there. Here is the log file with the Settings.MyD in the executable's directory:

Version: MyDefrag v4.1
Date: 2009/07/23 16:56:33
Windows version: v5.1 build 2600 S
Commandline: "C:\Program Files\MyDefrag v4.1\MyDefrag.exe"  -r "C:\Program Files\MyDefrag v4.1\Scripts\FastOptimize.MyD"
Working Directory: C:\Program Files\MyDefrag v4.1\Scripts
InstallPath = C:\Program Files\MyDefrag v4.1\
---> See the 'MyDefrag.log' file for information intended for endusers. This is the debug
---> logfile. The contents is highly technical and not documented. See the 'Debug' setting
---> or the '-d' commandline option to control the level of information in this file.
16:56:33 Analyzing the commandline.
16:56:33   Commandline argument '-r' accepted, added 'C:\Program Files\MyDefrag v4.1\Scripts\FastOptimize.MyD' to the scripts.
16:56:33 Running script: Language.MyD
16:56:33 Running script: C:\Program Files\MyDefrag v4.1\Scripts\FastOptimize.MyD
16:56:33 Executing rule: <Statements> ::= <Statement> <Statements>
16:56:33   Token[0] = Rule = <Setting> ::= RunScript '(' String ')'
16:56:33   Token[1] = Rule = <Statements> ::= <Statement> <Statements>
16:56:33 Executing rule: <Setting> ::= RunScript '(' String ')'
16:56:33   Token[0] = Symbol('RunScript')
16:56:33   Token[1] = Symbol('(')
16:56:33   Token[2] = Symbol('String')
16:56:33   Token[3] = Symbol(')')
16:56:33 Running script: Settings
16:56:33   Locating file: Settings
16:56:33     Looking in the directory of the main script: Settings
16:56:33     Looking in the directory of the executable: C:\Program Files\MyDefrag v4.1\Settings
16:56:33     Read key 'SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\MyDefrag_is1\InstallLocation' from registry: 'C:\Program Files\MyDefrag v4.1\'
16:56:33     Looking in the installation directory: C:\Program Files\MyDefrag v4.1\Settings
16:56:33     Looking in %ProgramFiles%: C:\Program Files\MyDefrag v4.1\Settings
16:56:33     Looking in %ProgramW6432%: %ProgramW6432%\MyDefrag v4.1\Settings
16:56:33     Looking in %ProgramFiles(x86)%: %ProgramFiles(x86)%\MyDefrag v4.1\Settings
16:56:33     Looking in the PATH for: Settings
16:56:33     Found: C:\WINDOWS\system32\Settings
16:56:33   Loading file into memory: C:\WINDOWS\system32\Settings
16:56:33   Could not open handle: [5] Access is denied.
16:56:33   Stopping....
16:56:33   Finished executing the script.
16:56:36   Resetting ScreenSaverTimeout to 300
16:56:36   Resetting PowerOffTimeout to 120

[amk]

Looks like searching file "Settings", not "Settings.MyD"

[jeroen]

No luck there either.

Wauw. I am surprised at this problem, I should have anticipated this. There is a folder called "Settings" in your path ("C:\WINDOWS\system32\Settings" to be precise) and MyDefrag is trying to load that folder as if it was the Settings.MyD file. Not a file in that folder, but the folder itself. Which fails, ofcourse, and sadly enough without a proper error message. The "RunScript('Settings')" command in all the standard scripts will first look for the filename "Settings", and if not found it will append ".MyD" and search again.

So, there is a very simple solution to your problem: change the "RunScript('Settings')" command in all your scripts into "RunScript('Settings.MyD')". I will be doing the same.... and I will add some extra error messages to the program. There is no such folder on any of the computers I tested, which explains why I never ran into this problem myself.

[peters40]

Could this be why when i run MyDefrag the "PreventPowerSaving(yes)" and PreventScreenSaving(yes) did not work from Settings script, but work if i put them in the Fastupdate or SlowOptimise script?

[nin28]

Made those changes to the scripts and programs works like it should Thanks for everyone's help.

[amk]

Is MyDefrag search first file "Settings" in all directoryes, then file "Settings.MyD" in all directoryes?
More sensible first look first folder for file "Settings" then "Settings.MyD". After look second folder for both files and so other.