Thanks! IR7 working on two computers! On primary desktop I have previous IR5 and oops went to notification status 0 rearm IR7 work on second PC at notification but first PC give error at RE when typing E:IR7 "drive.vbs(4, 1) Microsoft VBScript runtime error: Wrong number of arguments or invalid property assignment: 'hex' Please do I need reinstall W7 or how to make IR7 work? cheers!
Hey RD, My latest build is really cool. To uninstall IR5 just remove the task(s) and any folder in that might be in the systemdrive? I forget if I had put the folder in systemdrive yet? Did you try C:IR7, or D:IR7 MS's RE changes drive letter so that is why I put all those alternatives TS
I find hidden folders IR6 and Trial which contain IR7.vbs / IR7.bat, removed. Use IR7 to remove then install then it reboot to RE auto. Same error at E:IR7 W7 Ent SP1 / 0rearms / notification / genuine warning / black desktop Please recommend ? I search and do not find this problem before
hello everyone, i have a question i think i didnt really unterstand how Rearm Wizard works.. probably because my english isnt the best lol i had no problems installing it, everything went well but i saw entries in windows task scheduler about rearm wizard so my question, does rearm wizard start with windows on every startup? could it slow down the startup? thanks
It's just a quick check. Only if action is required it will do further steps (rearming or telling you the 180 days are up if rearms exhausted).
Two tasks run at logon and I say this is not problem If they detect notifications they rearm and restore theme/wallpaper which is done silently although you will see control panel open up and theme restore then control panel will close Any non-genuine msg's also are closed at startup if in notifications
From your screenshot it looks like your VBScript is shot. It might have to do with missing DLL or OCX registrations.
Do you how to reinstall VBScript registrations? Google recommends to reinstall application that uses VBScript.
Unfortunately I don't have first-hand knowledge with VBScript, but you could try the following tip I found in the 'net (command shell with Admin rights!): Code: regsvr32.exe jscript.dll regsvr32.exe vbscript.dll regsvr32.exe wshom.ocx regsvr32.exe msxml3.dll regsvr32.exe -i shell32.dll regsvr32.exe OLEAUT32.DLL Then reboot.
Received an error on wshom.ocx but all others registered properly. Thanks, but still receiving error message
This questions has probably been answered but I had no luck finding it so my apologies in advance. Does this Rearm tool rearm automatically, or is there a box or something that pops up once a month and asks me to rearm? Thanks in advance.
Hello and sorry to bother... Thanks for the brilliant concept of unlimited rearming, constant trial and your efforts in your script. I am unlucky that it does not work for me: I just refreshed my Ultimate SP1 with MBR regenerator 4.5 after it had fallen into "black Nagscreen" state while IR7 was installed. It resulted in a trial system for 30 days. There are no error messages during installation and run of IR7, so hopefully I can get some help here. I suspect it may depend on my configuration: It is a triple boot by Easy BCD: C:\Windows XP pro D:\Windows 7 Ultimate G:\data partition some other Linux partitions I install IR7 from user account with administrator rights, computer reboots into RE, I choose C:\IR7 - executed. Result: Windows 7 with black nagscreen desktop The file "IR7.bat" is really in C. As Windows 7 resides in D: I copied it to D: and ran it again. Interestingly the RE did not find IR7 under D:, but under E:, which makes me think that there is a confusion of drive letters and the action of IR7 does not find the targets in Windows 7. In had the impression the time was a bit longer, but no effect on the Windows 7 installation, still black nagscreen. So I feel pretty helpless. Maybe I use MBR regen again and hope to get it sorted within the coming 30 days. Thanks and curious about your suggestions.
Hi shaban55, I will try to help you... First MBR regen is not necessary when using Rearm Wizard as it does not deal with bootsect at all, only loaders do Second RE has a bug in it that changes drive letter so it makes sense why E:IR7 worked and why I put those extra options If there is no watermark on the desktop then your in a 30 day rearm and you just need to reset the desktop theme to usual Once it is set to your theme will be put in here Code: C:\windows\resources\themes Then you can go into C:Trial/IR7 and click the IR7.bat file and watch the IR7.theme file show up or you can reboot/logoff/on and it will also show up, then you should be set for the theme stuff Note: The IR7.bat that IR7 uses to reset the rearms is temporary just for IR7 reinstall, and the IR7.bat in C:\Trial\IR7 is permanent and used every logon to check if rearm is needed and thus consequentially theme/wallpaper restore Hope that helps TS
Thanks, time surfer for this immediate answer! I tried it again on a Windows 7 in the 30 days trial state with 4 rearms left. The result is a watermarked (not genuine) but not black desktop. The state of activation is not displayed anymore. The most puzzling for me is that I do not have this c:\trial folder which you mentioned. Nothing visible happen on startup. I am also unclear about this reset of the wallpaper. Does it not happen automatically? Maybe something unrecognized happens during installation. Seems I have to stick with DAZ loader.... Kind regards shaban55