Hi Jeroen,
Just wondering whether you have any date for your next version. We tried 4.3.1 but had to back out to 4.2.9 (most stable version) as we were experiencing a high number of crashes.

We still get the odd crash in 4.2.9 and from previous reads through the forum all appear to be known issues.

Thanks Owen.

JK,
Sorry to confuse you. We installed 4.3.1 but backed it out (back to 4.2.9), which is where we ran into the inno issue.

We backed out 4.3.1 due to crashes which according to some other threads were known issues due to be fixed in a later mydefrag release.

To date, v4.2.9 has proven stable and reliable.

Hope that clears things up. Thanks

["A problem with "Not Implemented" errors when Setup or Uninstall was run on Windows 7 under special conditions such as from a non-interactive service was fixed."]

JK,
Thanks for this thread & update. We also ran into this problem and thanks to those who have updated this thread see that the fix is in 5.3.7 on inno.

Just to complete the thread and so others may see what the specific issue relates to..

Per http://www.jrsoftware.org/files/is5-whatsnew.htm

"A problem with "Not Implemented" errors when Setup or Uninstall was run on Windows 7 under special conditions such as from a non-interactive service was fixed."

In our situation, we use a service to initiate the inno package and encounter exactly this.

Thanks

JK, Thanks for that, some good tips, will review and look at various options. For the record we dont house myd scripts as I have a perl wrapper utility that I have bundled data that contains the myd scripts that we use so the ONLY myd files required on the servers are mydefrag.exe and our wrapper utility.

This of course has the disadvantage for when you change some of the script options where me may be required to update the myd bundled data, but a small price to pay for a tidy stand-alone package.

We also control scheduling via our own custom scheduler product and dont use the GUI or screen saver options.

But thanks again for the tips, esp the 64bit heads-up, as we do have a mix of both and that @#$! registry redirection always gets me

Cheers

[NOTE:]

Thanks guys but I dont think thats exactly what I want for cleaning up earlier installed versions> I have created a small cmd script that as long as you know what versions to cleanup you simply set VER.

This will remove the old files and remove the product from the Add Remove Program files list within control panel (eg below)

NOTE: Caution is if you have NOT installed mydefrag in the default location (ie. you have installed in a custom folder where other software resides then dont use this as it will remove all content from sub-dirs and files within that location)

=== START OF SCRIPT ===
@echo off
setlocal

set VER=4.2.3
set MYDEFRAG=MyDefrag v%VER%_is1

for /f "delims=\ tokens=7" %%a in ('reg query hklm\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall') do (
   if "%%a" equ "%MYDEFRAG%" (
     for /f "tokens=1,3" %%b in ('reg query "hklm\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%MYDEFRAG%" /s') do (
       if "%%b" equ "InstallLocation" (
         :: remove the install path
         echo Delete directory %%c
         rd /s /q %%c
         :: remove the add program files from the control panel list
         echo Delete registry hive for hklm\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%MYDEFRAG%
         reg delete hklm\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%MYDEFRAG% /f
       )
     )
   )
)
=== END OF SCRIPT ===

Thanks for that.
But when using the uninstall commandline, how do I control what previous version is going to be uninstalled as we now have several. Or am I missing the point completely and running this un-installs all known versions?

[Batch Script]

Hi, I'm sure I'm joining the ranks of "not another one asking this..."

I'm aware that mydefrag install process does not clean up earlier installed versions but wondering whether anyone out there has found a nice simple and clean method that can be achieved via commandline.

We have several hundred servers and perform installs via a central repository server and perform software installations remotely using a in-house custom method. Basically the command line is below (under "Batch Script")

As part of this script I would like to be able to remove the mydefrag versions from the Control Panel - Program File list. I can probably use wmi or reg type stuff and create a small VB or perl wrapper script to do this but I would prefer to simply add to the small cmd file. I dont have any issue with setting vars containing the previous version ID's.

Thanks

Batch Script
@echo off
set MYDEFRAGVER=4.2.9

c:\cardinal\bin\MyDefrag-v%MYDEFRAGVER%.exe /verysilent /suppressmsgboxes /norestart /noicons /dir="c:\cardinal\bin" /log="c:\cardinal\logs\mydefrag_install.log"
sleep 3
del /q c:\cardinal\bin\MyDefrag-v%MYDEFRAGVER%.exe

JK, Thanks for the 4.2.8 version. Unfortunately we will not be able to use this version as I read the post regarding maxruntime not working, which we rely on so will need to wait for your release that corrects this.

Are you able to indicate an eta release date?

I would also like to thank you for your software and support which is very good and I have requested my company to make a donation to you, for this.

Looking forward to your next version 

JK,
First off, thanks for a great version (4.2.7). We have just started rolling out and so far have not encountered ANY issues (as opposed to the crashes from earlier versions).

I have just recently presented a review summary to management on the progress of myd implementation and was asked a question..."What is the user base for MYD"? The management team are of the opinion that a product is likely to be more reliable and better supported if it has a significant user base (rightly or wrongly).

Anyway, do you have any idea, possibly from download statistics, an estimate on how many copies of MYD are in use? Alternatively, number of downloads?

I appreciate that you will have a mix of corporate & personal users , but any stats that you have on your distribution would be appreciated.

Thanks

Hi jeroen, we have had a few of these occurring also, running v4.2.6 and I have been following this post.

I didnt see any point submitting logs at this stage and was waiting for your updated diag version. Do you have any eta on the next version? Thanks

Oh, slightly embarrassing , if there was every a case of RTFM…guilty!! .. and thanks.

works fine.....MyDefrag-v4.2.3.exe /verysilent /suppressmsgboxes /norestart /noicons /dir="c:\cardinal\bin" /log="c:\cardinal\logs\mydefrag_install.log"

@jeroen, Hi, we have been experiencing some server lockups that I think you have addressed in (4.2.2) ,which is great! I was wondering whether you could consider a new feature to do with installation.

We have over 200 servers to perform installs on when new releases come through and we have a wrapper utility that initiates mydefrag via commandline and controls scheduling based on each servers processing requirements. We do not use the GUI.

For installation I would like to have something along these lines..

Distribute the installer exe (eg. MyDefrag-v4.2.3.exe) to a common location on all servers, which are distribution software would do.

Run the installer in silent mode via a centralized command initiator, which we would do.

When the installer runs it install in %ProgramFiles%\mydefrag (without the version extension)

Possibly achieve this via a new commandline arguement to the installer to retain requirements for users that require ability to revert to earlier versions (if need be).

We do not require any myd sample scripts to be installed as our wrapper utility generates these from a generic data deck within the wrapper, so we really only need the commandline executable and any other files that will satisfy the licencing agreement, possibly achieve this by a second new commandline argument –commandlineonly.

Reason for asking this is that we have a policy to remove any old versions of software when upgraded, where possible (MS always get us on this one). We have centralized software that can distribute files to all servers and execute commandline scripts to cleanup files, but it is still quite time consuming. We maintain a centralized software repository that contains the mydefrag versions previously used and if we ever need to revert to an earlier version we can do so by rerunning our centralized distribution\installation process of the earlier version.

As usual your comments and feedback appreciated.
Regards Owen.

Great...thanks for the speedy response also.

Hi, Realize you are are still reviewing the memory issue for drive with lots of files\compressed dirs etc but is there any way that we can change this behaviour so rather than commandline runs generating popups that mydefrag simply sets an exitlevel and terminates? We have mydefrag running from another utility that monitors other server processes and will terminate mydefrag if other heavy disk i/o processes start, but the wrapper utility can not tell and action the background popup. Our preferred option for batch processes is not to have popups and for exceptions to log exceptions and terminate.

Sorry, I should also mention that we have not yet distributed any part of mydefrag to our managed servers , apart from our masters (for testing), but would be prepared to distribute the installer once ready to move into production, without installing if that would satisfy the licence requirements. Thanks