Falo Posted February 2, 2013 Share Posted February 2, 2013 (edited) V 1.4.1.14I don´t know if it´s just here this happens.I have selected to integrate a bunch of drivers and tweaks plus removed "extra themes" and "Speech and Natural Language" under Vlite.But after I have pressed "start" it stands still on "Removing selected folders" for about 20 minutes thenWinToolkit stops working.I have tried three times now and same result (same in 1.4.1.13 and 12 (I think) too).I went back to 1.4.1.8 and it worked flawless...Done after 1h and 31min/Falo Edited February 2, 2013 by Falo Quote Link to comment Share on other sites More sharing options...
Legolash2o Posted February 3, 2013 Share Posted February 3, 2013 What Windows are you using and what Windows are you trying to modify? Do you have a last session preset?UPDATE 1: The only text saying 'Removing selected folders' is when you have selected 'Delete support folder' or 'Delete upgrade folder'.UPDATE 2: I will be releasing a test version, please try it Quote Link to comment Share on other sites More sharing options...
Falo Posted February 3, 2013 Author Share Posted February 3, 2013 (edited) Hi! I use Win 7 Ultimate x64 and here is last preset. /Falo2013-02-02_18-43-07_Mac Drivers_Tweaks.ini Edited February 3, 2013 by Falo Quote Link to comment Share on other sites More sharing options...
Legolash2o Posted February 3, 2013 Share Posted February 3, 2013 As i thought (check above), you have Delete 'Support' folder and Delete 'Upgrade' folder selected. Try the test version (linked below). Quote Link to comment Share on other sites More sharing options...
Falo Posted February 3, 2013 Author Share Posted February 3, 2013 We wrote at the same time Lego. Thanks! I´ll try the test version and yes I have the 'Delete support folder' and 'Delete upgrade folder' selectedas you said. /Falo Quote Link to comment Share on other sites More sharing options...
Falo Posted February 3, 2013 Author Share Posted February 3, 2013 (edited) I am trying the test version now ( WinToolkit141-15_Test1 ) and it hangs on "Removing 'Support' Folder".Not there quiet yet but near /Falo Sorry my bad! I hadn´t added the test version to "trusted" applications in the firewall.It was running in the "Sandbox".I started over again (not in the sanbox) and now it works Thanks!!! /Falo Edited February 3, 2013 by Falo Quote Link to comment Share on other sites More sharing options...
Falo Posted February 3, 2013 Author Share Posted February 3, 2013 Hi (again) The test version (WinToolkit141-15_Test1) worked fine.Done in 1h and 9min compared to 1.4.1.8 that took 1h and 31min for the same operation. Maybe you have done some performance tweaks between the versions. I must say this is a really great program and "hat off" for fast response when problemsappear. Keep up the good work :beerchug: /Falo Quote Link to comment Share on other sites More sharing options...
Legolash2o Posted February 3, 2013 Share Posted February 3, 2013 Your welcome, glad it's sorted. Quote Link to comment Share on other sites More sharing options...
bphlpt Posted February 3, 2013 Share Posted February 3, 2013 We've got to get the word out better that one of the first things to try, besides double checking the file MD5, if Win Toolkit doesn't work correctly is to temporarily disable ALL anti-virus and sandbox type programs. Then make sure you are running Win Toolkit as an Admin and all work folders are as close to the root of the drive as possible with as short a path name as possible. Don't use paths like - C:\The most ridiculous path name\I can possibly\come up with\Just for me\Just to make life difficult\I'll put Win Toolkit here\ - Instead use something like - C:\WTK\. Cheers and Regards Quote Link to comment Share on other sites More sharing options...
compstuff Posted February 3, 2013 Share Posted February 3, 2013 I agree 1000% and if I can add: I know the toolkit handles spaces but I really think its good practice to NOT put spaces in the directories and names, even if they are short. c:\win kit\ versus c:\winkit\We've got to get the word out better that one of the first things to try, besides double checking the file MD5, if Win Toolkit doesn't work correctly is to temporarily disable ALL anti-virus and sandbox type programs. Then make sure you are running Win Toolkit as an Admin and all work folders are as close to the root of the drive as possible with as short a path name as possible. Don't use paths like - C:\The most ridiculous path name\I can possibly\come up with\Just for me\Just to make life difficult\I'll put Win Toolkit here\ - Instead use something like - C:\WTK\. Cheers and Regards Quote Link to comment Share on other sites More sharing options...
crashfly Posted February 3, 2013 Share Posted February 3, 2013 It is a shame that WinToolKit cannot pop up with standard things to try if it detects errors in certain places. Just a generic listing something like what bphlpt just mentioned. Of course that would take a bit of work. Maybe a "standard troubleshooting" button for the unaware? Quote Link to comment Share on other sites More sharing options...
Legolash2o Posted February 3, 2013 Share Posted February 3, 2013 We've got to get the word out better that one of the first things to try, besides double checking the file MD5, if Win Toolkit doesn't work correctly is to temporarily disable ALL anti-virus and sandbox type programs. Then make sure you are running Win Toolkit as an Admin and all work folders are as close to the root of the drive as possible with as short a path name as possible. Don't use paths like - C:\The most ridiculous path name\I can possibly\come up with\Just for me\Just to make life difficult\I'll put Win Toolkit here\ - Instead use something like - C:\WTK\. Cheers and Regards 1. When a user clicks 'Start' it prompts the user to disable the anti-virus. 2. WinToolkit does detect this and refuses to open. 3. WinToolkit works fine with spaces. If foreign characters are detection, then they will be copied to the temp folder to be worked with. Quote Link to comment Share on other sites More sharing options...
bphlpt Posted February 4, 2013 Share Posted February 4, 2013 Spaces aren't the only issue. Sometimes it's the resulting path length. If you end up with a path length >256 characters it can create problems for you. Even if Win Toolkit is able to finish everything without error, if you then try to copy or move that folder elsewhere on your system, Windows itself might complain. I have run into this even with Win7 x64. Not if it's just the ISO, but rather if you expand it. It's always safer to keep the path length a short as possible. Cheers and Regards Quote Link to comment Share on other sites More sharing options...
compstuff Posted February 4, 2013 Share Posted February 4, 2013 I have run into path length issue many times on my Win7x64 laptop so I definitely agreeSpaces aren't the only issue. Sometimes it's the resulting path length. If you end up with a path length >256 characters it can create problems for you. Even if Win Toolkit is able to finish everything without error, if you then try to copy or move that folder elsewhere on your system, Windows itself might complain. I have run into this even with Win7 x64. Not if it's just the ISO, but rather if you expand it. It's always safer to keep the path length a short as possible. Cheers and Regards Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.