OK, maybe IR6/7 doesn't need backups but I do I usually make a backup right after install/configuration of the system and then a second one after installing and maybe updating all programs (everything I need except graphics drivers). Can I simply reinstall or uninstall/install IR6 again, after more than 180 days then, when I overwrite my system with one of the backups or will something lock me off then?
One of my many designs/concept was to make user have to uninstall before re-installing but with the new code user will actually be able to re-install without uninstalling Trick to IR7 is to make sure the 30 day task is always reset after install or rearming so that the task is in sync with the 30 day rearm countdown although this is automatic with the way I designed IR7 I think you'll be fine!
I used ir6 and that was the result : View attachment 24130 I do all steps recommended by instructions of the program
May I ask if this is a clean install? Have you used other solution prior? There are some tools here that can fix your system files as it is unusual for a default key to not work Try opening cmd prompt as admin again and run this cmd please Code: sfc /scannow Also in the Daz threads there is a tool called WATfix or something I forget and I believe Josh Cell also has a system repair tool IR6 is usually known for having very little troubleshooting so I'm guessing you have corrupt system file and when fixed should work fine Talk to you later
Yes , but can not remember what i used. scan reveals corrupt files can not be fixed and details in : C:\Windows\Logs\CBS but the cbs.log can not be opened
timesurfer - do I read the signs correctly that are you in the beta-testing process of shifting this project over to what you dubbed 'Rearm Wizard' based on IR7, one feature being a query message after 180 days "Do you want to refresh your rearm count?" Right now I still find Duality 420 (only with IR6 references in the script code) on the first page, and from what I know no alert message feature after 180 days, right? Thanks for clarifying, and for your hard work!
You will get the 180 message and the install will work if you click yes but the uninstall won't work! It will say uninstalled and give error msg's and you'll still have to delete the IR7 folder and maybe the Trial folder since the latest uninstall code when you click uninstall in the Rearm Wizrd/IR7 console does work just not the uninstall connected to the windows yes/no msg box Since I am alone in my project for the time being, I decided to apply a name change I've been wanting to make for some time. The major changes are a concept that I came up with that would allow users to use my rearm concept in an completely automatic way. s1ave77 provided most of the code for my idea although i have not seen him around lately? Given his code worked well for my idea there was still an problem with a batch console flashing at boot to provide for possible user interaction. As good as that was and in it being my project I decided to take it one final step further. To have a silently run batch file to just to back ups for theme/wallpaper then user would not see at startup a batch console. They would only see a batch console flashing at startup if the main IR7 task which rearms automatically and silently every 30 days was missed due to users computer being off when that task was scheduled to run. So I developed the concept to split the backup/rearm-restore code in two pieces thus user would rarely see a flashing batch console unless again their computer was off when the IR7 was suppose to run I haven't had the time to finish phase 2 of the backup/rearm-restore concept but should have some time soon I believe?! Also there is still one bug I'm working on with the uninstall code for my backup/rearm-restore concept I don't know yet how to write the uninstall code for the backup/rearm-restore but possible with some help or some insight on how to do it it too will get done soon Thanks for your query Take care TS
I'm still visiting, sadly I don't have any time for testing, currently. And I suck at code, as you know.