I have searched the web high and low and I can not find a copy of dbug_undo.cmd. I installed dbug and now I can't get it off. Every time I go to the site to download it, they only let me get the install part of dbug. Can someone please help me? I have been working on this for the last 3 hours now and I'm sooo tired of this.
Which dbug are we talking about?
Have you contacted Nick Shaw, the creator of dbug? I will see if I can contact him for you.
Aaah, FoolishIT dbug.
I know that if you select the blank dbug file (DOS version) it will restart your system and the dbug_undo.cmd will automatically show up.
Does it not do that if you run the dBug.exe?
It should be created once its run, but he said he don't have dbug_undo.cmd
Yea I didn't when I downloaded it had to use the DOS version to make it appear.
Try this
Open notepad and type
@"%~dp0\dBug.exe" -u
save as dbug_undo.cmd
I do apologize for the trouble, and I received message from Britec earlier (thanks for the heads up, sorry I'm late!) but I've been out of town and was on the road.
I'm curious about the circumstance in which you first ran dBug.exe, but I'll go ahead and state that there are some obvious flaws in dBug usage right now, and you may fit into one of these categories I'm about to explain. In v2.0, rather than having to keep multiple files together, I just had dBug.exe create the dBug_Undo.cmd file itself when run, at the same time it installs the reminders to run the undo at Windows startup!
It is supposed to create the undo file in the current directory, and it was supposed to be a simple convenience. I'm not sure how this didn't occur to me previously, but one could (and I can see a need for this) run it from a write protected flash drive or similar, a path where the current user doesn't have full (e.g. write) permissions, or run it even directly from the .zip file. In these cases it would certainly fail to write the undo file.
Another thing I'm not sure why this didn't occur to me previously, but I could simply have dBug.exe just do the "undo" without the help of the command line parameter (in the batch file which is dBug_Undo.cmd) by having it simply check for the values it created on any run, and if they exist already it removes them, and if not, that's when it would create them and reboot.
In fact, I just had some other good ideas for it now that I'm thinking about dBug again. Expect a new dBug release very soon to address these issues, and I'll check back here to make sure everything is ok.