Some software claims to be portable, but how do we know if it is really portable or not? I remembered back in the days when everyone was using Windows 98, a lot of “hacking tools” especially nukers are just one single executable file but it still requires dependency files such as winsck.ocx, msvbvm60.dll and etc. If those DLL or OCX files are not registered in your system32 folder, you won’t be able to run the program.
Microsoft is making their OS’s more secure
Depending on your background, you may find different sections of the newly published Microsoft Security Intelligence Report (SIR) to be of more interest. In today’s post, we would like to highlight the section on infection rates based on the operating system (OS) version and the service pack level. Microsoft has consistently observed that machines with newer OS and with more recent service packs are less likely to be infected by malware. The graph below shows the number of computers having malware removed per 1,000 executions of the MSRT on that OS/SP during the second half of 2008 (2H08).
In the SIR, you will find the the following conclusions based on this data:
- The infection rate for Windows Vista is significantly lower than that of its predecessor, Windows XP, in all configurations.
- Comparing the latest service packs for each version, the infection rate of Windows Vista SP1 is 60.6 percent less than that of Windows XP SP3.
- Comparing the RTM versions of these operating systems, the infection rate of the RTM version of Windows Vista is 89.1 percent less than that of the RTM version of Windows XP.
- The infection rate of Windows Server 2008 RTM is 52.6 percent less than that of its predecessor, Windows Server 2003 SP2.
- The higher the service pack level, the lower the rate of infection. This trend can be observed consistently across client and server operating systems.
There are two reasons for this:
- Service packs include all previously released security updates. They can also include additional security features, mitigations, or changes to default settings to protect users.
- Users who install service packs generally maintain their computers better than users who do not install service packs and may also be more cautious in the way they browse the Internet, open attachments, and engage in other activities that can open computers to attack.
Server versions of Windows typically display a lower infection rate on average than client versions. Servers tend to have a lower effective attack surface than computers running client operating systems as they are more likely to be used under controlled conditions by trained administrators and to be protected by one or more layers of security. In particular, Windows Server 2003 its successors are hardened against attack in a number of ways, reflecting this difference in usage.
If you’re dying to try out Windows 7 but aren’t ready to give up your installation of XP or Vista, let’s take a look at how to dual boot Windows 7 with XP or Vista.
Preliminary tasks: Download the Windows 7 Beta and Burn It to a DVD
Assuming you’ve already downloaded a fresh copy of Windows 7, you’ll need to burn it to a DVD in order to do a fresh installation. To handle this task, grab a copy of my favorite CD and DVD burning tool called “ImgBurn”, burn the ISO to a DVD, and move right along to step 1.
Step 1: Partition Your Hard Drive
Before you go installing Windows 7, the first thing you need to do is create a new partition on your hard drive to hold the new installation of Windows. Partitioning your hard drive will vary depending on whether you’re running XP or Vista—namely because Vista has a partition tool baked in, XP does not.
Partition Your Hard Drive in XP
To partition your hard drive in Windows XP, you’ll need to download some sort of third-party partitioning software. I prefer to the GParted live CD, a free, open source boot CD that can handle all kinds of partitioning duties.
To use it, just download the GParted Live CD, burn it to a CD, then reboot your computer (booting from the disc). You’ll boot right into the partitioning tool.
Resize your current OS drive to free up enough space for a Windows 7 partition (the minimum system requirements ask for 16GB).
Create a new partition from the newly freed space.
Apply your changes.
Partition Your Hard Drive in Vista
The folks at Redmond were kind enough to include a disk partitioning tool in Vista if you know where to look. So go to:
- System and Maintainence (skip this one if you’re in Classic view)
- administrative Tools
- Computer Management.
Once you launch the Computer Management tool, click on Disk Management under the Storage heading in the sidebar. It’s partitioning time.
Step 2: Install Windows 7
Now that you’ve done all the heavy lifting, it’s time for the easy part: Installing Windows 7 on your new partition. So insert your Windows 7 disc and reboot your computer (you’ll need to have enabled booting from your DVD drive in your system BIOS, but most PCs will have this enabled by default).
Once the DVD boots up it’s a simple matter of following along with the fairly simple installation wizard. When you’re choosing installation type, be sure to select Custom (advanced) and choose the partition you set up above.
Be careful here. Choosing the wrong partition could mean wiping your other Windows installation altogether, so make sure you pick the new partition you just created.
After you select the partition, go grab yourself a drink and let the installer do its work. Windows will run through some installation bits, restart a few times in the process. Eventually you’ll be prompted to set up your account, enter your license key, and set up Windows.
Windows XP usually plays nicely, but occasionally you do the odd recalcitrant box that doesn’t want to play nice with the other computers, and share.
If you’ve ruled out the Windows Firewall (Make sure that Windows File Sharing has a checkbox in there for allowed), and everything else looks correct, but it still isn’t working, try the following:
As we need the NTRights program, and it doesn’t come with XP, download and install the administration tools from one of these locations. Don’t worry about the name, the Kit works fine on XP also:
Once installed, please do the following:
- Click Start, Run (or Press Windows R)
- Type cmd and click OK
- In the DOS window (the black screen that just appeared), type the following:
- net user guest /active:yes
- ntrights +r SeNetworkLogonRight -u Guest
- ntrights +r SeNetworkLogonRight -u Everyone
- ntrights -r SeDenyNetworkLogonRight -u Guest
- ntrights -r SeDenyNetworkLogonRight -u Everyone
- Reboot, and try again. It should work.
Couple of things to know
There are two main things that you have to do to schedual Powershell scripts.
- Allow Interactive Commands using set-executionpolicy command.
- Put Powershell script in a ".ps1" file. You can use any text editor to make this.
The first thing you need to do is make sure that Powershell is set to execute Powershell scripts, instead of only allowing interactive commands to be run in the Powershell environment.
Type the following at the Powershell command prompt:
This will allow the system to run Powershell scripts that are created locally (Remote Powershell scripts that may be downloaded must be signed).
Once this is done, you can create your Powershell script using notepad. Just make sure you name the file with an extension of .ps1 . Now to run the script outside of its Powershell environment you type a command similar to the following:
powershell -command "& 'MyScript.ps1' "
Just put the above command into a .bat or .cmd file and schedule it like you would normally schedule a script to be run with Windows task scheduler.