DiskMax 2.2

[NELyon]

Hmm... since my previous post got deleted from the "Wipe-Out" of the forum (lol)

I have also taken a look at the current code, and only two calls to FileSetAttribute are called. Both of which come nowhere close to touching the desktop. I would say the only problem is the programs that the script calls (Namely... Microsoft Programs. )

So, instead of blaming this behavior on the program, Blame it on Microsoft!

[Kohr]

Ok everything got wiped and I don't feel like remembering everything I posted.

I used Office 2000 and WinXP on the PC that this occurred on. I also remember that I ran this program from the desktop. I can post it when I get back to work Monday if you want. I have no idea what "combination" of events made this happen but at the most I would have Firefox and Outlook running at the time I started this. Within 2 seconds of it running all the files on my desktop disappeared so I hit ESC to cancel this.

I have been working in software QA for 10+ years and I know what I saw and what it did.

I am mainly pointing out what happened to me and others can do with this information what they want.

Unless you want more information from me about the PC that this happened on then I doubt I will post in this again.

Kohr

[Valik]

Why don't you people stop bitching and offer to help figure out why this is happening? Running to the forum making accusations and carrying on like a six year old throwing a temper tantrum isn't doing anybody any good.

Edited February 17, 2007 by Valik
Typo.

[testingtest]

Why don't you people stop bitching and offer to help figure out why this is happening? Running to the forum making accusations and carrying on like a six year old throwing a temper tantrum isn't doing anybody any good.

your right I just wish somebody could fix my problem though I lost a lot of stuff.

John I didn't blame well I sort of did but when it happens to two people you should put up a warning or close the script for now

until the problem is fixed. I think you should also add options of what it can and can not delete I don't think it should pull a rambo

and start deleting stuff but thats up to you although you should tell the users what it does exactly.

I would love to get feed back on the fix for this problem and again I don't want to blame you but my computer was find until I

tried your script

[testingtest]

heres some quick info for who ever is interested in helping me/us.

I don't see the files on my desktop but when I make a new folder it was named folder 5

and when I renamed the folder to something I use to have it said that the name already exist.

I just think the files got hidden but not sure were to look, I went in my c drive

and went to all users desktop and said show hidden files but that didn't help.

[Valik]

The files are set as system and hidden. You have to enable "Show Protected Operating System files" to see them.

[testingtest]

The files are set as system and hidden. You have to enable "Show Protected Operating System files" to see them.

I hate to be a pain but can you guide me on how to go about this.

hehe your all to smart for me

edited:

aww I found it but that didn't help

Edited February 17, 2007 by testingtest

[randallc]

Hi,

offer to help figure out why this is happening?

I thought that was the point; there is no way to offer to help here as there is no available script The only thing anyone can do is report what has happened to them and request help urgently! I don't think it is fair to call that "bitching" when most other posts here include a script. I would certainly offer some help if I was included! - @Koshy John says he will not allow the code to be seen under any circumstances!

I have also taken a look at the current code

How are you doing that without a passphrase!? - makes a mockery of protection, I guess!

Best, randall

Edited February 17, 2007 by randallc

[Valik]

Hi,

I thought that was the point; there is no way to offer to help here as there is no available script

There's no source code available for AutoIt, either, but we manage to do okay at resolving issues. In some cases where only the user could reproduce a problem, we've given them non-official builds with fixes in place so they could test the issue. The fact that the source code isn't available means finding and fixing the issue is harder, not impossible and it definitely doesn't mean others can't help.

The only thing anyone can do is report what has happened to them and request help urgently! I don't think it is fair to call that "bitching" when most other posts here include a script.

I call what's going on bitching. Nobody is coming on saying "The script did this, how can I help you fix it?" People are saying, "Your script did this, you suck posting malware, pull the download link, fix my problem." Big difference.

I would certainly offer some help if I was included! - @Koshy John says he will not allow the code to be seen under any circumstances!

So? That's his right. He wrote the code, it belongs to him. He can do whatever he wants with it. Your attitude that "I won't help because I can't see the code" is very draconian.

How are you doing that without a passphrase!? - makes a mockery of protection, I guess!

My guess is he is using a hacked version of the decompiler.

[KJohn]

Official Notice

- Everyone who's seen the code for this program cannot imagine how anything like what happened to the 3 (unfortunate) users could ever happen.

- 17 people downloaded the program yesterday bringing the tally to 385, no complaints from any of them.

From what I gather, these incidents are very very isolated and are possibly caused by something special on those 3 user's systems. To diagnose this correctly, one step could be to get your system tested for performance, viruses and spyware at http://www.pcpitstop.com

Please register there and include a link to the test results page of your system (which should list the programs installed on your system and display a set of running processes and their purpose). This could possibly help with debugging other problems elsewhere too.

@the 3 people who've experienced problems

Please run the following 2 lines of autoit code in a separate script and tell me if what happened the first time repeats. These are the only two attribute setting lines in the entire code.

FileSetAttrib(@HomeDrive&"\Documents and Settings\All Users\Application Data\Microsoft\OFFICE\DATA\*","+RSH")
FileSetAttrib(@HomeDrive&"\Program Files\Hewlett-Packard\Digital Imaging\*.tmp","+RSH",1)

If the situation repeats, the problem can be isolated to the way AutoIt or Windows handle these instructions. Looking forward to your feedback.

[randallc]

Hi,

@Valik,

I won't help because I can't see the code

Not saying that!

"I can't help very much because I can't see the code" - of course I'll report all i can, best I can, but can't help much else?

the code @Koshy John has above worries me a lot; and I think it is possibly the problem; has it been fully tested for behaviour if the directories he uses/ the macro he uses do not exist?

Best, randall

[testingtest]

I know it is a closed source and thats his right but I think people who request the source should be able to see it I think someones computer is more important then anyones source code. I don't want to acuse anybody for this accident but crap happens.

I don't know what I am trying to apply here but I hope someone can find a fix for this.

If this problem has happened to other please post the fix not only for me but for others

[KJohn]

I know it is a closed source and thats his right but I think people who request the source should be able to see it I think someones computer is more important then anyones source code. I don't want to acuse anybody for this accident but crap happens.

I don't know what I am trying to apply here but I hope someone can find a fix for this.

If this problem has happened to other please post the fix not only for me but for others

;again so that you don't have to go back to the previous post
FileSetAttrib(@HomeDrive&"\Documents and Settings\All Users\Application Data\Microsoft\OFFICE\DATA\*","+RSH")
FileSetAttrib(@HomeDrive&"\Program Files\Hewlett-Packard\Digital Imaging\*.tmp","+RSH",1)

[testingtest]

;again so that you don't have to go back to the previous post
FileSetAttrib(@HomeDrive&"\Documents and Settings\All Users\Application Data\Microsoft\OFFICE\DATA\*","+RSH")
FileSetAttrib(@HomeDrive&"\Program Files\Hewlett-Packard\Digital Imaging\*.tmp","+RSH",1)

man I love ya problem fixed. I am sorry for making you go through the troble a programmer should look into this.

I am sorry if it seemed I was being a dick

[KJohn]

man I love ya problem fixed. I am sorry for making you go through the troble a programmer should look into this.

I am sorry if it seemed I was being a dick

@testingtest

Its ok. I know from experience how frustrating it is to lose your files. And its only because you made such a fuss that the issue was looked into very urgently.

@Valik

There seems to be something weird about the FileSetAttrib() function. It is either not working as expected or its not been documented properly enough. Please look into it before other coders run into problems far more serious than this.

NOTE TO ALL USERS

All outstanding issues have been resolved.

Please standby while an updated version of the code is compiled and uploaded.

[testingtest]

@testingtest

Its ok. I know from experience how frustrating it is to lose your files. And its only because you made such a fuss that the issue was looked into very urgently.

@Valik

There seems to be something weird about the FileSetAttrib() function. It is either not working as expected or its not been documented properly enough. Please look into it before other coders run into problems far more serious than this.

NOTE TO ALL USERS

All outstanding issues have been resolved.

Please standby while an updated version of the code is compiled and uploaded.

really your a good guy sorry for the hazzle. I looked at this line of code and played with it, and read the help file a few times and still stikes me odd but the good staff of autoit should clear that up

[KJohn]

All issues in the code to date have been fixed. View first post in this thread for new features. If you are running the program currently without issue, you will be prompted to download it (automatically) 30 days from your install date. So within a month, everyone will be running the new version. Cheers!

@Valik: The FileSetAttrib() function thingy still remains. What is going to be done about it? I've filed a bug report. Waiting for a reply.

[randallc]

All issues in the code to date have been fixed. View first post in this thread for new features. If you are running the program currently without issue, you will be prompted to download it (automatically) 30 days from your install date. So within a month, everyone will be running the new version. Cheers!

@Valik: The FileSetAttrib() function thingy still remains. What is going to be done about it? I've filed a bug report. Waiting for a reply.

Hi,

Sounds good; so what have you done to fix it? -Did you just check if directory exists before fileattrib?

Does this fix the re-run Diskmax problem after viewing interrupted log too?

Best, Randall

[KJohn]

Hi,

Sounds good; so what have you done to fix it? -Did you just check if directory exists before fileattrib?

Does this fix the re-run Diskmax problem after viewing interrupted log too?

Best, Randall

Yes that's exactly what i've done for now.. and i suggest other coders here use it too until the problem is resolved.

The re-run problem must be fixed now... I wouldn't know if it helps unless you test it out since you were the only one to face that problem. Your cookie request has be included, if u didn't notice.

The only 'issue' now is you cannot reset your preferences unless you remove the registry entries manually. I will include that functionality soon... Had to get this version out to fast to solve the bugs... Put in as many features as I could in the very short time I allowed myself...

I hope you like it... And anyone facing any problems or wanting new features are requested to reply to this thread!

[Valik]

I know it is a closed source and thats his right but I think people who request the source should be able to see it I think someones computer is more important then anyones source code.

This is a very stupid thing to say. Based on your logic, I should be able to demand to see the source code for Windows since it can screw up my computer, too.