Items filtered by date: December 2015

Overview

First let me start by saying that one of the main features of Windows Vista is the new user accounts security enhancements, but sometimes, defaults don't meet everyone's taste when it comes to how we deal with our PCs. I for one, always used full administrator accounts since I first knew what a Windows user account is, and never been hit by a virus/spyware/crap, using common sense and updated AV software, so I don't want to give permissions to myself or face strange error messages every time I do a simple task on my computer.

We know UAC feature in Windows Vista, and we all know how to disable it, this is not the purpose of this thread, because even after you disable UAC, you'll have other prompts about folder/file permissions errors sometimes (I faced it in strange, unexpected occasions, like deleting an empty folder for a program left by the uninstaller), or you'll need to right click and select "Run as Administrator" for most applications to work/install correctly.

That's because Microsoft made the administrators accounts (in local administrators group) run as standard users, unless we give permissions for every and each administrative tasks, with a little difference when UAC is turned on/off.

Enough introductions, lets get our hands dirty:

Remember that cute "Administrator" account you see when you login to safe mode in XP? That's the built-in administrator account that's installed by default, and disabled by default too, after a little digging-in I made this tutorial that'll let you enable and use this account in normal mode, and with a little other tweak, enjoying an XP-like administrator experience, while UAC is left ON (or off, it doesn't matter), but with no prompts or right clicks.

For Windows Vista Ultimate/Business/Enterprise:

1- Click Start, and type "secpol.msc" in the search area and click Enter. (You may receive a prompt from UAC, approve/login and proceed)

2- In the left list, choose "Local Policies", then "Security Options"

3- Set "Accounts: Administrator account status" to Enabled.

4- Set "User Account Control: Admin Approval Mode for the Built-in Administrator account" to Disabled.

For Windows Vista Home Basic/Home Premium:

1- Click Start, and type "cmd" in the search area, right click on "Command Prompt" and select 'Run as Administrator".

2- In the command prompt type "net users Administrator /active:yes" (Note the capital "A" in Administrator) and press Enter, you will get a confirmation as "The command completed successfully".

3- Click Start, and type "regedit" in the search area and click Enter, navigate to: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System] Double click on "FilterAdministratorToken" and set it to "0"

---

Now log-off, and you'll see new account named "Administrator" is available, click on it to login.

Now you are the master of your domain! I recommend if you're going to use this method is to apply it as soon as you do a fresh install of Windows, so you can simply delete whatever administrator you've created in the setup process, and make this one the "real" administrator for your PC, also you can rename this new admin account or change its password like any other account from "User Accounts" in the Control Panel.

 

A last note/disclaimer:

Please note that disabling UAC and using the built in Adminstrator account will also disable IE7 "Protected Mode", fore more information and a work around please see this post.

NiCad

These batterys discharge after time and have something called 'battery memory' this is where a battery if not kept fully charged will have a tendancy not to hold a full charge.

Suggestions:

Charge the battery fully and then Discharge fully / use till dead

It can be helpful to overcharge (leave on the charge for longer than needed by up to 20%). 

These will reduce battery memory and prolong life. A NiCad battery left discharged will not last as long as a charged battery

Lithium Ion

With these batterys it does not matter from what level they are charged from they will not suffer from a battery memory, however a Lithium Ion battery that is left fully charged will not last as long as an uncharged battery.

Suggestions:

Leave battery fully discharged when it will not be used for a long time.

1. Insert the Windows XP CD into the CD-ROM drive.

2. Click Start, and then click Run.

3. In the Open box, type d:\i386\winnt32.exe /cmdcons where d is the drive letter for the CD-ROM drive.

4. A Windows Setup Dialog Box appears. The Windows Setup Dialog Box describes the Recovery Console option. To confirm the installation, click Yes.

5. Restart the computer. The next time that you start your computer, "Microsoft Windows Recovery Console" appears on the startup menu.

The NT BOOT diskette allows you to boot from a floppy using the NT OS Loader menu to select the NT partition to load the kernel from. This can be very handy if you have lost your NT boot sector by installing another OS which copies over the partition boot record.

Supports up to 2 harddisks (any partition).

The steps are:

1. Format a floppy disk using a Windows NT 4.0, 2000, XP or Server 2003 machine (not windows 9x!) format a: /u

2. Copy NTDETECT.COM and NTLDR onto the floppy disk

3. Download this BOOT.INI file and put it onto the floppy disk

 

BOOT.INI file

[boot loader]
timeout=-1
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="First harddisk, first partition" /sos
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="First harddisk, second partition" /sos
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="First harddisk, third partition" /sos
multi(0)disk(0)rdisk(0)partition(4)\WINDOWS="First harddisk, fourth partition" /sos
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Second harddisk, first partition" /sos
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="Second harddisk, second partition" /sos
multi(0)disk(0)rdisk(1)partition(3)\WINDOWS="Second harddisk, third partition" /sos
multi(0)disk(0)rdisk(1)partition(4)\WINDOWS="Second harddisk, fourth partition" /sos
C:\="Previous Operating System on C:\" 

---

This boot.ini assumes that windows is installed in the "WINDOWS" folder, for terminal server you must edit the boot.ini and replace all "WINDOWS" into "WTSRV", for Windows NT 4.0 you must edit the boot.ini and replace all "WINDOWS" into "WINNT".

This boot.ini will not work for SCSI Controllers without a SCSI BIOS (need NTBOOTDD.SYS on the diskette)

Done, try and boot it!

Vaseline Method

1. Clean the surface of the screen.
2. Take some Vaseline and fill the scratch with it.
3. Gently wipe off the excess Vaseline, being careful not to press too deeply so as to leave some inside the scratch.
4. Voila. This works because the optical density more closely matches the LCD face than air.

Pencil Eraser Method

1. Find a pencil with a clean, soft eraser. It must have no pencil graphite on it as you won't want to smudge that on your monitor.
2. Lightly rub the eraser over the scratch or nick on the screen.
3. Keep rubbing until the scratch completely disappears.

Warnings

• Users report mixed results with these method.

List of the environment variables callable in windows 2000. e.g. Open a cmd prompt and type echo %appdata% which should return the full path to your profile's Application Data directory. If calling from a batch file remember to quote the %variable% e.g.

IF EXIST "%appdata%"\workrave\historystats. (mkdir D:\AllMyFiles\Workrave.) ELSE echo Workrave. missing

Here's the list with percentage included:

ALLUSERSPROFILE	%ALLUSERSPROFILE%	Local returns the location of the All Users Profile.
APPDATA	%APPDATA%	Local returns the location where applications store data by default.
CD	%CD%	Local returns the current directory string.
CMDCMDLINE	%CMDCMDLINE%	Local returns the exact command line used to start the current cmd.exe.
CMDEXTVERSION	%CMDEXTVERSION%	System returns the version number of the current Command Processor Extensions.
COMPUTERNAME	%COMPUTERNAME%	System returns the name of the computer.
COMSPEC	%COMSPEC%	System returns the exact path to the command shell executable.
DATE	%DATE%	System returns the current date. This variable uses the same format as the date /t command. Cmd.exe generates this variable. For more information about the date command, see the Date command.
ERRORLEVEL	%ERRORLEVEL%	System returns the error code of the most recently used command. A non-0 value usually indicates an error.
HOMEDRIVE	%HOMEDRIVE%	System returns which local workstation drive letter is connected to the user's home directory. This variable is set based on the value of the home directory. The user's home directory is specified in Local Users and Groups.
HOMEPATH	%HOMEPATH%	System returns the full path of the user's home directory. This variable is set based on the value of the home directory. The user's home directory is specified in Local Users and Groups.
HOMESHARE	%HOMESHARE%	System returns the network path to the user's shared home directory. This variable is set based on the value of the home directory. The user's home directory is specified in Local Users and Groups.
LOGONSERVER	%LOGONSERVER%	Local returns the name of the domain controller that validated the current logon session.
NUMBER_OF_PROCESSORS	%NUMBER_OF_PROCESSORS%	System specifies the number of processors installed on the computer.
OS	%OS%	System returns the OS name. Windows XP and Windows 2000 display the OS as Windows_NT.
PATH	%PATH%	System specifies the search path for executable files.
PATHEXT	%PATHEXT%	System returns a list of the file extensions that the OS considers to be executable.
PROCESSOR_ARCHITECTURE	%PROCESSOR_ARCHITECTURE%	System returns the processor's chip architecture. Values: x86, IA64.
PROCESSOR_IDENTIFIER	%PROCESSOR_IDENTIFIER%	System returns a description of the processor.
PROCESSOR_LEVEL	%PROCESSOR_LEVEL%	System returns the model number of the computer's processor.
PROCESSOR_REVISION	%PROCESSOR_REVISION%	System returns the revision number of the processor.
Program Files	%PROGRAMFILES%	returns the location of the default install directory for applications.
PROMPT	%PROMPT%	Local returns the command-prompt settings for the current interpreter. Cmd.exe generates this variable.
RANDOM	%RANDOM%	System returns a random decimal number between 0 and 32767. Cmd.exe generates this variable.
SYSTEMDRIVE	%SYSTEMDRIVE%	System returns the drive containing the Windows root directory (i.e., the system root).
SYSTEMROOT	%SYSTEMROOT%	System returns the location of the Windows root directory.
TEMP	%TEMP%	System and User return the default temporary directories for applications that are available to users who are currently logged on. Some applications require TEMP and others require TMP.
TMP	%TMP%	System and User return the default temporary directories for applications that are available to users who are currently logged on. Some applications require TEMP and others require TMP.
TIME	%TIME%	System returns the current time. This variable uses the same format as the time /t command. Cmd.exe generates this variable. For more information about the time command, see the Time command.
USERDOMAIN	%USERDOMAIN%	Local returns the name of the domain that contains the user's account.
USERNAME	%USERNAME%	Local returns the name of the user currently logged on.
USERPROFILE	%USERPROFILE%	Local returns the location of the profile for the current user.
WINDIR	%WINDIR%	System returns the location of the OS directory

I guess I should first make clear what a messy URL is, and what a clean URL is. Here's a messy URL:

http://www.desiquintans.com/index.php?page=articles

And here's a clean URL:

http://www.desiquintans.com/articles/

Notice how much nicer the last one looks. Clean URLs are great for 6 reasons:

1. They look prettier
2. They are easier to remember
3. They help you save filespace on pages which have many links
4. They are easier to link to, both for you and for other webbies
5. They help cut down on typos because there is less confusion about what exactly to write and type

And the really big reason as to why you should use clean URLS:

6. They allow search engines to spider your site.

Why are spiders so picky?

Search engine spiders usually stay away from messy URLs because chances are the code is really bad on whatever script you use and the spider could become stuck in a loop, requesting the same pages over and over and draining you of your bandwidth.

.htaccess is your friend

Anyway, how do we make our URLs clean? Well, you need a server that runs Apache. This solution only works for Apache servers, so Win2k users have to go somewhere else for their kicks.

The first step is to make an .htaccess file. It doesn’t need to be anything fancy.

1. Open Notepad or EditPad Lite or whatever the hell you use to make plain text files (that is, a program with no text formatting)
2. Save a new blank document as .htaccess

There’s your .htaccess file.

.htaccess hackery

Now for the actual commands. The ․htaccess is really just a container that holds the commands that you want Apache to execute. Paste this into your file:

RewriteEngine On

That tells Apache to turn mod_rewrite on, but I don’t know anything about that, and you don’t need to either.

Now figure out the query string that your site’s messy URLs use. My example was http://www.desiquintans.com/index.php?page=articles, so my query string is index.php?page=articles. This would be what I put in my .htaccess:

RewriteRule ^([a-zA-Z0-9]+)/$ index.php?page=$1

RewriteRule explained

Let me explain the components of the above command.

The caret (the ^ symbol) means “all the stuff before this.” It’s the URL where this particular .htaccess file is located, so if you put it in www.x.com/hi/ it will stand for www.x.com/hi/, and if you put it in www.x.com's public folder, it will stand for www.x.com.

([a-zA-Z0-9]+) is a variable set that means, “any amount of characters that are lowercase alphabetical, uppercase alphabetical and numerical.” The stuff inside the square brackets is the variable itself, the plus sign outside the square brackets tells it that any amount of characters is fine. If I didn’t have the plus sign I would only be allowed one character in each clean URL. A list of common variables is at the bottom of the page.

$ means that this is the end of the clean URL, and that the messy one that Apache is supposed to fix up is following. Please note the slash just before this dollar sign -- you can either leave it out or keep it, but it’s best to do both in their own RewriteRules.

$1 is the number of a specific variable. Since I have only one variable set ( ([a-zA-Z0-9]+) ) I only need to specify one variable. If I had several variable sets, like section/([a-zA-Z0-9]+)/page/[0-9] then I would have to specify $1 and $2 variables.

Save the .htaccess file and upload it to your root public directory—the directory with your main index page.

My .htaccess file

My sample .htaccess file has this:

RewriteEngine On  
RewriteRule ^([a-zA-Z0-9]+)$ index.php?page=$1  
RewriteRule ^([a-zA-Z0-9]+)/$ index.php?page=$1

Notice that the two RewriteRules allow the user to have a trailing slash or no trailing slash when they enter a URL. You should allow for both of these instances, because there isn’t a person alive who won’t skimp on a slash when they think they’re accessing a directory. A clean URL is not a directory—it’s just a redirected messy URL.

Common variable sets

• [A-Z] The variable can have uppercase letters
• [a-z] The variable can have lowercase letters
• [0-9] The variable can have numbers
• ([a-zA-Z0-9]+) The variable can have any of the above, and has no limit to the number of characters.

Windows Vista All Versions x86 OneClick Activator by CLoNY

This crack enable user to bypass the product activation requirement of Microsoft Windows Vista x86 by emulating hardware-embedded BIOS ACPI_SLIC license information of so called "Royalty OEMs".

In combination with a matching product key and OEM certificate this allows for rendering any system indistinguishable from a legit pre-activated system shipped by the respective OEM.

This crack doesn't use vstaldr Grup multiboot boot loader to load the emulation driver during initial boot up of system but is completely software based Windows driver whichruns within Windows Vista operating system environment.

 

Instructions

1. Install RTM or Retail Windows Vista x86 WITHOUT product key.

2. Once Vista is installed extract the zip files.

3. Excute file "VistaActivator" and follow video instructions. (If Windows ask you select "Allow").

4. AFTER Reboot Windows will be activated.

 

Crack Notes

1) If you want to check if crack worked:

Click Start, Control Panel, System (for classic view of Control Panel).

Click Start, Control Panel, System and Maintenance, System (for normal view of Control Panel).

2) If it is not already activated click on Change product key and put these keys according to the version that you installed:

Ultimate: 6F2D7-2PCG6-YQQTB-FWK9V-932CC
Business: 72PFD-BCBK8-R7X4H-6F2XJ-VVMP9
Home Premium: 8XPM9-7F9HD-4JJQP-TP64Y-RPFFV
Home Basic: 743HW-QD98X-TQVXJ-8RKRQ-RJC9V

Click Next and windows vista is activated.

 

Vista Loader 2.2.0 OEM BIOS Crack Emulator

Instructions how to install VistaLoader for clean installation of vista.

1. install windows vista with the serial below.

2. after that, log into vista and extract vistaloader.rar into a folder. eg c:\vistaloader

3. run comand prompt with administrator access.

4. browse into c:\vistaloader eg. cd\vistaloader

5. type install.cmd [oem]

6. reboot your machine...and you are activated...

• replace [oem] with asus, hp, acer ,lenovo, sony or dell. eg. if you are using dell, just type install.cmd dell in the command prompt with administrator acess.

asus
~~~~
ultimate: 6f2d7-2pcg6-yqqtb-fwk9v-932cc
business: 72pfd-bcbk8-r7x4h-6f2xj-vvmp9
home premium: bh436-xt3fk-mjkjh-6gqt2-qxqmf
home premium: 8xpm9-7f9hd-4jjqp-tp64y-rpffv
home basic: 2wp98-khth2-kc7kg-4yr37-h8phc
home basic: 743hw-qd98x-tqvxj-8rkrq-rjc9v

acer
~~~~
home premium: 2tybw-xkcqm-xy9x3-jdxyp-6cj97

hp
~~
ultimate: 6f2d7-2pcg6-yqqtb-fwk9v-932cc
home premium: 2r6wf-kyf88-27hyq-xtkw2-wqd8q
home premium: gp3fq-jb647-7cw8f-h646b-7pmgf

lenovo
~~~~~~
home premium: 34bkk-qk76y-wwr7c-qf2m7-2tb37

dell
~~~~~~
home premium : 4gptt-6ryc4-f4gjk-kg77h-b9hd2
business : 368y7-49ymq-vrcty-3v3rh-wrmg7
ultimate : 2qbp3-289mf-9364x-37xgx-24w6p

Systems with BIOS dated prior to July 1994(504 MB Limitation).

Typically these BIOS will have a 504 megabyte (1,024 cylinder) limitation. Prior to this date, most manufacturers' BIOS did not provide the Logical Block Address (LBA) feature needed for proper translation. Some BIOS had LBA mode in the setup, but the feature did not work properly.

 

Systems with BIOS dated after July of 1994 (2.048 GB Limitation).

Typically, these BIOS provide support for hard drives with capacities larger than 504 megabytes. However, depending on the manufacturer's release date and version number, different limitations may be encountered. The major limitation that surfaces is the 4,093-4,096 cylinder limitation. This barrier is derived from the fact that some BIOS manufacturers implemented Logical Block Addressing (LBA) translation in their BIOS with a 4,093 - 4,096 cylinder limitation. System hangs would occur when the cylinder limitation threshold is exceeded. A system hang is defined when the operating system hangs during initial loading, either from floppy diskette or existing hard drives. If these symptoms of system hang occur or there are questions whether the system BIOS will support the drive, contact the system or motherboard manufacturer for assistance.

 

4.2 GB Limitation.

The maximum parameters at the 4.2 GB barrier are 8,190 cylinders, 16 heads and 63 sectors for a capacity of 4.2 GB. A system hang is defined when the operating system stops responding during initial loading, either from floppy diskette or existing hard drives. This can be caused by the BIOS reporting the number of heads to the operating system as 256 (100h). The register size DOS/Windows 95 uses for the head count has a capacity of two hex digits. This is equivalent to decimal values 255. If these symptoms of system hang occur or there are questions whether the system BIOS will support the drive, contact the system or motherboard manufacturer for assistance.

 

8.4 GB limitation.

The maximum parameters at the 8.4 GB barrier are 16,383 cylinders, 16 heads and 63 sectors for a capacity of 8.455 GB. To go beyond this boundary, a new extended INT 13 function is needed from the BIOS as a support feature for the drives. The BIOS listed below are all "CORE" BIOS that will support drives larger than 8.4 GB. Even though a BIOS is dated correctly or is the current version, it may not be able to support extended interrupt 13 because of modification done to the "CORE" of the BIOS from the motherboard manufacturer.

 

32 GB limitation.

This condition is caused by the Award BIOS inability to address hard drives greater than 32GB. Award has been made aware of this issue and has fixed their "core" BIOS as of 6/99. They are passing this information along to the motherboard manufacturers' that use their BIOS. Updates for the BIOS should be available soon from individual motherboard manufacturers' to correct this problem. The following are options to overcome this hang condition: Please contact your motherboard manufacturer, not Award, for a BIOS update. If your motherboard manufacturer does not have an update available, purchase the Maxtor Ultra ATA 100 adapter as an alternative solution. Maxtor Ultra ATA 100 "Where to Buy"

Install the Capacity limitation jumper (J46) and use the Maxblast Plus installation software to complete the installation. Please refer to hard drive Installation Instructions for location of this jumper or click here for an illustration of jumper locations. If your system still hangs after installing the J46 jumper, please run the file JUMPON.EXE. Note: If the BIOS is believed to fall within the following guidelines but does not support the drive, contact the system or motherboard manufacturer for a potential upgrade to their product.

American Megatrends INC. (AMI): BIOS versions with a date of January 1, 1998 or newer. Award: BIOS versions dated November 1997 or newer. Phoenix: Version 4 Revision 6 or newer. Note: Maxtor hard drives have a Cylinder Limitation Jumper to assist in the resolution of BIOS limitation issues. When this jumper is installed the MaxBlast Software must be used to complete the installation of the hard drive. Some Operating Systems will NOT function properly when the Capacity Limitation Jumper is applied (e.g., Windows NT, Linux, etc.).

Interrupts can have a nasty system-wide effect when hogging CPU and it can be worse than you realize. The problem is likely that your IDE ATA/ATAPI disk is running in PIO mode, which is the slowest, due to some time-outs or errors. To check and see if this is the problem, follow these steps:

 

1. Go to Device Manager (Right-click My Computer>Properties>Hardware Tab>Device Manager);
2. Expand IDE ATA/ATAPI Controllers and click on Primary IDE Channel;
3. Click Properties button and select the Advanced Settings Tab;
4. If the Transfer Mode is PIO and not DMA, this is your problem;
5. Leave Properties panel open.

Quick Method

A Microsoft Knowledge base says remove the IDE ATA / ATAPI driver...

Reboot twice and then problem is gone.

Longer Method (untested)

The fix is relatively quick and painless. It requires two successive reboots. Just make sure you follow these directions all the way to the end or the problem will come back.

 

1. Open Registry Editor (Start>Run> “regedit”>OK);
2. Expand HKEY_CURRENT_CONFIG/System/CurrentControlSet/Control/Class/{4D36E96A-E325-11CE-BFC1-08002BE10318};
3. Highlight 0001 and click Edit>New>DWORD Value;
4. Type “ResetErrorCountersOnSuccess” and hit Enter;
5. Click Edit>Modify;
6. Enter “1” into the Value Data and hit OK.

This should fix the problem with Interrupts and make your system run much better.

---

Also read DMA reverts to PIO, this provides causes and other fixes.