Jump to content

Featured Replies

Posted

DO NOT REPORT BUGS IN HERE!

 

The final version of the v1.x series has been released. My university degree depends on v2.x being successful, so I will be putting all my effort into that.

 

Bug Fixes

The only future releases of v1.x will just contain bug fixes. 

 

Requests

The request forum has already been closed.

 

Known Bugs

I've added more logging to help detect this.

 

 

Changelog

*1.5.2.15^FIX: Unattended 'Serial' did not update
*1.5.2.14^FIX: MaxDate error if Windows year is set to < 2013
*1.5.2.14^FIX: Potential duplicate folder path in RunOnce
*1.5.2.14^Better error logging
*1.5.2.13^FIX: Fixed potential RunOnce issues
*1.5.2.12^FIX: Fixed most too long silent installer path errors
*1.5.2.12^FIX: Fixed hanging at end of Update Catalog download
*1.5.2.12^Update Catalog code improvements
*1.5.2.11^FIX: Fixed incorrect name on Silent Installer
*1.5.2.10^FIX: No longer able to work on images with install.wim missing
*1.5.2.10^FIX: Temporary fix of Windows 10 image support
*1.5.2.10^FIX: Invalid options showing in WIM Manager
*1.5.2.10^FIX: Unmount Screen > Cleanup Manager text too big
*1.5.2.9^Added more logging on Update Catalog
*1.5.2.8^FIX: Fixed image not appearing
*1.5.2.7^FIX: AIO Move to top and bottom buttons
*1.5.2.5^FIX: Cleanup Manager via Capture Image error when no folder selected
*1.5.2.4^FIX: Object null on Cleanup Manager load
*1.5.2.3^FIX: Fixed parameter not correct when getting wim info
*1.5.2.3^FIX: Index -1 error when moving in AIO
*1.5.2.2^FIX: ISO Maker access denied error on DVDs
*1.5.2.1^FIX: Corrupt update detection
*1.5.2.1^FIX: Null error on update integration
*1.5.2.1^FIX: Access denied error on ISO extraction
  • Author

Just a heads up. Tomorrow (Sunday), I will be going through all the error logs and reports again to try and see what I can fix in v1.x. If you have made a bug report, please update it with any relevant details.

 

Sorry I have been on the forum much yesterday and today. I've been at some 2-day training and I still don't have a phone to check the forum, etc.. 2 months without a phone :-O

1.) Can you please remove protection for any new Post-Windows 8.1 (Windows 10's era) in Wintoolkit 1.x and release a version 1.5.30?

I read about version 2.x but I plan to stuck with version 1.x for a some time, so I don't have problem to work with abounded versions of some program or some alpha/beta build of Windows.

 

2.) And please one more thing - add checkbox "Do not show this message again." for annoying 'New DISM released' request.

 

3.) If you decide to release version 1.5.30 the last from branch 1.x development of WinToolkit... if so, please make the last version clean from protection and annoying message.

 

,thanks in advance

 

p.s. You make a GREAT software man, continue with good work!

Edited by MAXtoriX

......

2.) And please one more thing - add checkbox "Do not show this message again." for annoying 'New DISM released' request.

......

You can uncheck it under "Options" (Check for new DISM)!

 

Thiersee

Edited by Thiersee

  • 2 weeks later...
  • Author

The easiest way to describe it is... my IP was blocked due to many connections still open lol. It's sorted now.

 

I could access it via proxy but couldn't sign in. I could also access it via VPN but just slower and no access to FTP via the VPN. Was just an bog standard error 404, couldn't even ping it.

  • Author

Build 14 released publicly and build 15 released via test builds.

 

The important thing about build 14 is that it adds some more log details for errors. It adds the 20 last status message updates. (Integrating x of x : blah blah blah).

  • 1 month later...
  • Author

I've got all my coursework handed in and spent a lot of time on v1 today. I just got to finish off what I'm doing and I shall release a test build.

 

EDIT: I've done the changes. I will test and upload after Yoga and Body Pump :)

  • 2 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...