ZoneAlarm is free ... Offtopic: 5 min ago eartquake hit my town ... thanks god it was small one, but still a pretty good shaking of my desk with PC
Does it force you to install an anti-virus or anything like that? Does it nag you to purchase the full version? Is it a decent app?
Nope, AV is optional. And so is Defense+, this too can be disabled if all you need is a good firewall...
I wouldnt use VB for any thing hardcore like video or audio, photo manipulation but for small things like this it's fine, I might use it to code a UI for my carputer. I dont use a firewall on my windows machines, any sketchy apps get disasembled and inspected then run in a sandbox, then mabye in a virtual machine with a packet sniffer. if it still seems sketchy I delete it.
fixed a few bugs 1. if app was ran twice with out quitting in between runs, an already mounted system volume that was not C: would get dismounted. 2. bootinst.exe was being run durring uninstall, instead of bootsect.exe 3. added the SLIC in bootmgr for people to play with. 4. fix key install issue. 5. files are inside the .exe and are extracted as needed CAUTION: grldr and a modded bootmgr dont work together, you have to remove the modded bootmgr and replace with a unmodded one before you try to boot a grldr bootloader. this app will save the original bootmgr as bootmgr.orig and replace it when you choose to install a grldr bootloader, but another installer may not. some people cannot get permission to move bootmgr, this app will crash if it cant gain permision to move bootmgr.
Hi, just want to thank nononsense for this example-code, very nice. Indeed it gives novices( like me ) a good startingpoint... So thanks! Bye...
Hi, I wondered, do you know of any different ways to find the hidden system partition besides using wmi? I have only found about vds but thats a lot of code for it... Greetings
Ayup, if WMI is no good for you, old method was to look for a 100/200 MB partition. Another method was to do programmatic search all HDD for bootmgr filename. Yet another method was to search for a bootmgr file that matched the correct md5 hash. Basically WMI works best because it searches for the partition that is marked "SystemVolume", all the other ways are guess work and can affect certain dual boot users incorrectly. Could also try powershell, but all that stuff even confuses me sometimes.
Fixed OS detection issue on non-english systems found by alfawaves. changed from WMI to registry query which will also resolve some firewall software flagging the OS query as suspicious.
when you click the x button and installing or unistalling you get what it shows in the picture below this is my fix for it i dont know what other bugs it causes but im too lazy to figure it out Code: Private Sub Form1_FormClosing(ByVal sender As Object, ByVal e As System.Windows.Forms.FormClosingEventArgs) Handles Me.FormClosing Unmount() CleanUp() Dim pro As Process pro = Process.GetCurrentProcess pro.Kill() End Sub or you could tell the form to get rid of the control box when you click the install or uninstall buttons and have the control box come back after its done but thats for the original author to decide