crashfly

The tool is already a part of WinToolKit. It is under the "Main" tab and "Intermediate" sub-tab.

Been there. Done that. I have seen bad hard drives come and go. I understand your pain Legolash2o. I hope your computer gets fixed soon.

And a Happy Holdidays too!

At least it turned into a "white" christmas here. Happy Holidays everyone!

Thanks bphlpt, at least you figured out that much. I hope Legolash2o can simplify the confusion in the future.

Ok now .... looking at this thread, what is the newest version, 1.5.0.1 build 39 or 1.4.1.2?

While I do not know how you have it programmed, maybe something has changed in the function calls to resolve filename setting locations? Could be a bug in the programming language you use.

You know it is sad. The end of the world was on my birthday, and yet the world is still here. What is up with that?

Meh .... could be just sunspots. Maybe even that end of the world stuff. On the more serious side, yes you seem to have found a bug with the program. I am sure Legolash2o will find it and fix it as soon as he can.

What I meant by statistics were the sizes and not the speed.

Yowsers! I do not get by here as often as I should. Glad to see you have the "hosting" problem fixed Legolash2o. Hmmm .... I should stop by more regularly.

Maybe this needs to be studied a bit. Assuming that a user wants to integrate "all" of the latest updates, maybe some statistics need to be generated to see if using a RAM drive would even be feasable. I myself have 16gb of RAM and would set some aside for the program if necessary. (Although I also have a SSD, it might not even be worth it.)

Sounds like a UNC resolution issue. Possibly an undocumented "bug" with windows?

I am sure there are quite a few places that could possibly host the file, but most are not necessarily "easy" with the terms. Maybe asking the wincert site admins to allow a separate download for the "beta" WinToolKit would be in order. Just remember that WinToolKit was one of the original reasons why I donated to wincert. I hope this site never goes down.

I have seen this issue, although it is generally on the "older" motherboards that have the cap problem (and usually the capacitors have not literally 'blown' up). I have even replaced quite a few and have restored most to working condition. Sucks to hear though.

I would have to agree with this, how does one exactly add that header to any program in general? Does it depend on the programming language? Or is "patching" the the executable the way to do it?

How much do you consider a "reasonable" donation to get a keycode? I only ask this question because I am sure there are people that would attempt to take the 'sly' way out and donate very little (or as little as possible). I myself am unemployed, so I have to watch where my funds go carefully, but I would consider donating to your cause as I have used your program and like it very much.

Mmmmmm .... spam good! Oh, wait ... not that kind of spam. Yes, forum spam is bad. I have been well pleased with this forum being able to keep all of the spam posts at bay. Keep up the great work.

Yowsers, Kel! I hope things get better for you. It is not fun to lose a computer. Slightly off topic: How did your computer get "smoked"?

It is possible, but the process uses a program someone created of questionable legality. The forums over at mydigitallife would help you out on that, but I will not post a direct link here due to this forum's rules. What it is supposed to do is take the downloadable trial versions and combine them into a working install DVD while also changing the "channel" from trail to whatever you need it to be (pro, business, standard, etc). The program itself does not provide a key for you, but there are other questionable programs on that forum. Therefore, it is possible, just some licenses could be violated.

If you want to fix your system problems, it would seem to me that you need to start over from a *clean* system disk and then reinstall. Somehow what you seem to have is a corrupted install and using the "sfc /scannow" is not the best way to fix your problems. As for this problem, the "original" files are modified to have them perform whatever function was intended. A scan would restore the orginal because those files are "modified".

I hate to mention it, but yes Kelsenellenelvian is correct. It is difficult to understand your writing Makr0sha.man0b. It is one of the main reasons why I have not continued to help. How can I help if I do not understand you?

What version of WinToolKit were you using (you did not specify)? It could possibly be a bug, but then you might also want to include your last session file for Legolash2o to look at.

I am not sure about the "Common Files" directory, but I believe most of those directories can be specified from an autounattend.xml file. And that might be the only way that you can do it.

Are the registry settings modifying something in the "Local Machine" hive or the "Current User" hive. If the settings are modifying in the "Current User" hive, that at install is directed to the "Default User". It may be that those settings are not being carried over properly. If it is going to the "Local Machine" hive, then you possibly might have located a bug.