Why do we need it to run on XP? who dare using XP? no i'm kidding, but seriously I believe that there is no need to care about XP compatibly, since XP isn't compatible with this method of activation anyway...
i think its just to be safe and i still use xp on my laptop because it runs all my music production programs faster
I do some of my work on XP so, often times Im running this in VS while debugging, it should failsafe and with the only option to close the app.
i can live with the debugging error i just wanted to know if anyone knew how to stop it from happening
...just a quick question: I was looking at your source...looks ok...and came across your Unmount() procedure. Code: Public Sub Unmount() '================================================================================== 'unmount System Volume '================================================================================== Dim mountvol As New ProcessStartInfo("mountvol") mountvol.WindowStyle = ProcessWindowStyle.Hidden If isMounted = 0 Then If Not TargetDrive = "C:" Then mountvol.Arguments = (" " & TargetDrive & " /D ") Process.Start(mountvol) isMounted = 0 End If End If End Sub I was wondering why you check if "isMounted = 0", then set it to 0 within the code of the If block...? Because isMounted will already be 0 if it enters the If block, so the "isMounted = 0" seems unneeded... Or should the "If isMounted = 0 Then" be "If isMounted = 1 Then" instead? (that is my guess...)
He has to call the procedure for the If block to function. Although i'll be corrected if i am wrong lol.
I realize that...lol. My point is that he sets a variable to zero after he checks whether it is zero... Basically, isMounted must be zero to enter the If block... So why then set it to zero inside the If block if it already MUST be zero to even enter the If... Get me? Either "If isMounted = 0 Then" must instead be changed to "If isMounted = 1 Then" <which is what I think must be done...> ...or the "isMounted = 0" should be removed from inside the If block because it is pointless...
I follow you now. We'll just have to wait and see what he says about it. Been awhile since i used .Net
1 last question... (code from Target_Drive() function) Code: '================================================================================== 'mount System Volume '================================================================================== If isMounted = 0 Then For Each objMgmt In Volume.Get If objMgmt("SystemVolume") = True Then objMgmt("DriveLetter") = TargetDrive objMgmt.Put() isMounted = 1 '<--- set variable to 1 here since drive is now mounted...? Exit For End If Next End If Since you are using the "isMounted" variable to determine whether or not the system volume is mounted, should you then set isMounted = 1 within the If statement in the For loop (since it seems that you have apparently mounted the drive at this point)...or am I missing something? <see my comment in the code>
no hot carl is right what happend was the before the unmount code look liked this If Not TargetDrive = "C:" Then mountvol.Arguments = (" " & TargetDrive & " /D ") Process.Start(mountvol) isMounted = 0 End If but then it would unmount user mounted system volume, I felt that leaving the volume mounted if the user had manualy mounted it would be better so I changed it to what it is now, the extra isMounted = 0 was put there in the first place to deal with running the app over and over again without closing durring debugging.
OK...so you only use the isMounted variable to check whether the user has previously mounted the system partition before running the program...not whether the system partition is mounted at all... Got it, makes much more sense now. The variable name threw me off I guess.
what is the error, I cant read the small pixelated text you can remove the file decode and file check, but it will open up the risk of a resource replacement attack that could be used to install malware.
added Starter support added sony slic and certificate updated HP and Toshiba tosinv certificate to 2.1