If you're new here, you may want to subscribe to my RSS feed. So that you can read the latest updates about Web2.0 tools, Making Money Online, Tips in SEO, Ajax and many more. Thanks for visiting ProgramimiCOM!

Ever wondered just what that enigmatic name means?

Gaming and multimedia applications are some of the most satisfying programs you can get for your PC, but getting them to run properly isn’t always as easy as it could be. First, the PC architecture was never designed as a gaming platform. Second, the wide-ranging nature of the PC means that one person’s machine can be different from another. While games consoles all contain the same hardware, PCs don’t: the massive range of difference can make gaming a headache.

To alleviate as much of the pain as possible, Microsoft needed to introduce a common standard which all games and multimedia applications could follow – a common interface between the OS and whatever hardware is installed in the PC, if you like. This common interface is DirectX, something which can be the source of much confusion.

DirectX is an interface designed to make certain programming tasks much easier, for both the game developer and the rest of us who just want to sit down and play the latest blockbuster. Before we can explain what DirectX is and how it works though, we need a little history lesson.

DirectX history
Any game needs to perform certain tasks again and again. It needs to watch for your input from mouse, joystick or keyboard, and it needs to be able to display screen images and play sounds or music. That’s pretty much any game at the most simplistic level.

Imagine how incredibly complex this was for programmers developing on the early pre-Windows PC architecture, then. Each programmer needed to develop their own way of reading the keyboard or detecting whether a joystick was even attached, let alone being used to play the game. Specific routines were needed even to display the simplest of images on the screen or play a simple sound.

Essentially, the game programmers were talking directly to your PC’s hardware at a fundamental level. When Microsoft introduced Windows, it was imperative for the stability and success of the PC platform that things were made easier for both the developer and the player. After all, who would bother writing games for a machine when they had to reinvent the wheel every time they began work on a new game? Microsoft’s idea was simple: stop programmers talking directly to the hardware, and build a common toolkit which they could use instead. DirectX was born.

How it works
At the most basic level, DirectX is an interface between the hardware in your PC and Windows itself, part of the Windows API or Application Programming Interface. Let’s look at a practical example. When a game developer wants to play a sound file, it’s simply a case of using the correct library function. When the game runs, this calls the DirectX API, which in turn plays the sound file. The developer doesn’t need to know what type of sound card he’s dealing with, what it’s capable of, or how to talk to it. Microsoft has provided DirectX, and the sound card manufacturer has provided a DirectX-capable driver. He asks for the sound to be played, and it is – whichever machine it runs on.

From our point of view as gamers, DirectX also makes things incredibly easy – at least in theory. You install a new sound card in place of your old one, and it comes with a DirectX driver. Next time you play your favourite game you can still hear sounds and music, and you haven’t had to make any complex configuration changes.

Originally, DirectX began life as a simple toolkit: early hardware was limited and only the most basic graphical functions were required. As hardware and software has evolved in complexity, so has DirectX. It’s now much more than a graphical toolkit, and the term has come to encompass a massive selection of routines which deal with all sorts of hardware communication. For example, the DirectInput routines can deal with all sorts of input devices, from simple two-button mice to complex flight joysticks. Other parts include DirectSound for audio devices and DirectPlay provides a toolkit for online or multiplayer gaming.

DirectX versions
The current version of DirectX at time of writing is DirectX 9.22.1284. This runs on all versions of Windows from Windows 98 up to and including Windows Server 2003 along with every revision in between. It doesn’t run on Windows 95 though: if you have a machine with Windows 95 installed, you’re stuck with the older and less capable 8.0a. Windows NT 4 also requires a specific version – in this case, it’s DirectX 3.0a.

With so many versions of DirectX available over the years, it becomes difficult to keep track of which version you need. In all but the most rare cases, all versions of DirectX are backwardly compatible – games which say they require DirectX 7 will happily run with more recent versions, but not with older copies. Many current titles explicitly state that they require DirectX 9, and won’t run without the latest version installed. This is because they make use of new features introduced with this version, although it has been known for lazy developers to specify the very latest version as a requirement when the game in question doesn’t use any of the new enhancements. Generally speaking though, if a title is version locked like this, you will need to upgrade before you can play. Improvements to the core DirectX code mean you may even see improvements in many titles when you upgrade to the latest build of DirectX. Downloading and installing DirectX need not be complex, either.

Upgrading DirectX
All available versions of Windows come with DirectX in one form or another as a core system component which cannot be removed, so you should always have at least a basic implementation of the system installed on your PC. However, many new games require the very latest version before they work properly, or even at all.

Generally, the best place to install the latest version of DirectX from is the dedicated section of the Microsoft Web site, which is found at www.microsoft.com/windows/directx. As we went to press, the most recent build available for general download was DirectX 9.22.1284. You can download either a simple installer which will in turn download the components your system requires as it installs, or download the complete distribution package in one go for later offline installation.

Another good source for DirectX is games themselves. If a game requires a specific version, it’ll be on the installation CD and may even be installed automatically by the game’s installer itself. You won’t find it on magazine cover discs though, thanks to Microsoft’s licensing terms.

Diagnosing problems

Diagnosing problems with a DirectX installation can be problematic, especially if you don’t know which one of the many components is causing your newly purchased game to fall over. Thankfully, Microsoft provides a useful utility called the DirectX Diagnostic Tool, although this isn’t made obvious. You won’t find this tool in the Start Menu with any version of Windows, and each tends to install it in a different place.

The easiest way to use it is to open the Start Menu’s Run dialog, type in dxdiag and then click OK. When the application first loads, it takes a few seconds to interrogate your DirectX installation and find any problems. First, the DirectX Files tab displays version information on each one of the files your installation uses. The Notes section at the bottom is worth checking, as missing or corrupted files will be flagged here.

The tabs marked Display, Sound, Music, Input and Network all relate to specific areas of DirectX, and all but the Input tab provide tools to test the correct functioning on your hardware. Finally, the More Help tab provides a useful way to start the DirectX Troubleshooter, Microsoft’s simple linear problem solving tool for many common DirectX issues.

• 0 Comments

This bugged me for a few weeks before I found a solution. I was creating a file through FireFTP but Firefox crashed in the middle and the file was “half-created”. It exists on the Windows desktop as an empty file but it did not seem to fully exist on the hard drive. It just sits there on my desktop titled “i dont have 8gb free” teasing me because it knows I can’t get rid of it.

When I tried to delete it I got an error message:

Cannot delete file. Cannot read from the source file or disk.

So I know the file isn’t in use by any processes — the computer actually can’t find the file I’m referring to!

Here are things I tried and failed:

• Deleting through command line.
• Changing file permissions.
• Renaming the file (same error as above).
• Overwriting the file from different programs.
• Rebooting in safe mode and deleting from there.
• Booting into a Linux Live CD, loading up the NTFS drive reader to access the file.
• Clearing processes that may have been using the file.
• Running full spyware and virus scans.

I was at my wit’s end and about to install some shady third party application when I came across a solution on a newsgroup post:

The solution was simple, using the del command in a command prompt. I had tried this already of course but the trick was to not refer to the file by it’s full name, rather, refer to it by its 8-character “DOS name” also known as the 8dot3 file name. To find the 8dot3 file name, open command prompt and type:

dir /x

Note the 8 letter file name (most likely ending with ~1) and use the del command to get rid of it for good.

del idonth~1

I remember using 8dot3 names in DOS and older versions of Windows but it never occurred to me that this would make any difference when deleting files. Anyway, I’m glad I didn’t have to reinstall Windows just to get rid of this one immutable file sitting on my desktop! Hopefully this will help some of you in the future.

• 1 Comment

To run any of these apps go to Start > Run and type the executable name (ie charmap).

WINDOWS XP HIDDEN APPS:
=========================================

1) Character Map = charmap.exe (very useful for finding unusual characters)

2) Disk Cleanup = cleanmgr.exe

3) Clipboard Viewer = clipbrd.exe (views contents of Windows clipboard)

4) Dr Watson = drwtsn32.exe (Troubleshooting tool)

5) DirectX diagnosis = dxdiag.exe (Diagnose & test DirectX, video & sound cards)

6) Private character editor = eudcedit.exe (allows creation or modification of characters)

7) IExpress Wizard = iexpress.exe (Create self-extracting / self-installing package)

8) Microsoft Synchronization Manager = mobsync.exe (appears to allow synchronization of files on the network for when working offline. Apparently undocumented).

9) Windows Media Player 5.1 = mplay32.exe (Retro version of Media Player, very basic).

10) ODBC Data Source Administrator = odbcad32.exe (something to do with databases)

11) Object Packager = packager.exe (to do with packaging objects for insertion in files, appears to have comprehensive help files).

12) System Monitor = perfmon.exe (very useful, highly configurable tool, tells you everything you ever wanted to know about any aspect of PC performance, for uber-geeks only )

13) Program Manager = progman.exe (Legacy Windows 3.x desktop shell).

14) Remote Access phone book = rasphone.exe (documentation is virtually non-existant).

15) Registry Editor = regedt32.exe [also regedit.exe] (for hacking the Windows Registry).

16) Network shared folder wizard = shrpubw.exe (creates shared folders on network).

17) File siganture verification tool = sigverif.exe

18) Volume Contro = sndvol32.exe (I’ve included this for those people that lose it from the System Notification area).

19) System Configuration Editor = sysedit.exe (modify System.ini & Win.ini just like in Win98! ).

20) Syskey = syskey.exe (Secures XP Account database - use with care, it’s virtually undocumented but it appears to encrypt all passwords, I’m not sure of the full implications).

21) Microsoft Telnet Client = telnet.exe

22) Driver Verifier Manager = verifier.exe (seems to be a utility for monitoring the actions of drivers, might be useful for people having driver problems. Undocumented).

23) Windows for Workgroups Chat = winchat.exe (appears to be an old NT utility to allow chat sessions over a LAN, help files available).

24) System configuration = msconfig.exe (can use to control starup programs)

25) gpedit.msc used to manage group policies, and permissions

• 1 Comment

Ever wonder what makes a disc bad? Here’s why they vary in quality, and why you should worry about the discs you’ve entrusted with your data.

Burning CDs and DVDs is the easy part.

Knowing your data will be there when you go back to it days, months, or even years later–well, that’s a bit harder. Not all discs are created equal, as Fred Byers, information technology specialist at the National Institute of Standards and Technology, can attest.

Byers is part of a team heading up an independent study of DVD media quality. Based on the first wave of testing results, the situation is murky at best.

“We’ve found the quality varies, depending upon the type of dye used to make the write-once discs and [on the] the manufacturer,” reports Byers. Even discs from the same manufacturer, with the same brand, can test differently, Byers adds. “But there was more of a significant difference when you compared discs between manufacturers,” he explains.

DVD Media Quality: The First Tests

In the first phase of testing, completed late last year, NIST focused on the most popular media: write-once, single-layer DVD-R and +R discs. Rewritable discs will be tested in the second phase, slated to start this fall. An interesting footnote to the study’s methodology: NIST uses media purchased off store shelves and via Web sites; and while researchers are tracking the media by brand, they are not tracking the specific factory source of the media tested. For example, a given manufacturer’s discs could originate from different production lines, which could account for a variation in disc quality by the same manufacturer.

Hearing that there’s a difference between the generic, unbranded 100-spindle value-pack of media purchased online and the branded offerings you might find on a Best Buy store shelf is not surprising. After all, as David Bunzel, president of the Optical Storage Technology Association, points out: “With a generic product, there’s no consumer recourse. It’s buyer beware.”

If a disc isn’t properly manufactured, the consequences can be dire. At best, the disc will fail immediately during the burn process; this is a best-case scenario because then you know from the start that the disc is faulty. At worst, you may get an abundance of errors during the burn process. These errors won’t interrupt the burning process, and since write-once and rewritable DVD media have built-in error correction to compensate for scratches and other abnormalities on the disc (as do their CD cousins), any errors will be virtually invisible to you. You’ll only know they’re there if you use a disc diagnostics program, such as those offered by Ahead Software or Plextor. Nor will these errors affect the playback of the disc–initially.

Down the road, however, such invisible-to-the-eye errors can reduce the effectiveness of a DVD’s built-in error correction so that if some other issue develops on your disc, such as a scratch, you could end up with an unreadable disc when you go back to it months or years later.

But what would cause such a wide disparity in media quality between branded discs from the same vendor?

“We don’t know why it’s different–it could be a different dye, it could be a different manufacturing process,” notes Byers. “Manufacturers are constantly trying to improve their dye formulas–in theory improving the disc.”

Nonetheless, at the same time, competitive forces are driving manufacturers to find ways to economize on production costs. And cost-cutting measures can result in discs that don’t perform as well as those generated during an earlier production run, either in terms of failing outright or not burning at the maximum possible speed on a given DVD drive. “It varies over time, as the output changes,” Byers says.

Brand Disparity

As for the disparity between brands that NIST found, the distinguishing factors come down to quality control and the dyes used in disc production. Declining to name names, Byers points out that “some manufacturers make their own discs, and some purchase them from someplace else–which opens you to variations in the manufacturing plant, or changes in the source [of that media].”

Vendors like Maxell and Verbatim manufacture discs on their own production lines, as do Asian manufacturers CMC Magnetics, RiData, Taiyo Yuden, and others; other name brands contract with a third-party manufacturer to produce discs to their own specs; and still others just buy third-party-produced media wholesale, without imposing their own set of quality controls on the media production.

The intricacies of disc production and quality control aren’t the only variables that seem to affect media. More surprising is the number of discs that seem to have a propensity for specific hardware.

“One thing we’ve found in compatibility testing [of DVD-R and +R media] is that it’s a relationship between a specific brand of media and the manufacturer of the hardware,” observes Byers. “There was no one drive that played every single type of compatible media, and there was no one media brand that played perfectly in every drive.”

And, he adds, sounding as frustrated as any consumer might, “You can’t say there’s a clear, delineated set of reasons as to why.”

A Grading System?

One of the most common questions I hear is, “What’s a good brand of media to buy?” DVD and CD media are so commonplace nowadays that it’s easy to forget the complexities that go into producing them. And if anything in that production process is off, it could, in time, affect the integrity of the data you’ve burned to a disc.

“It’s very tough to answer that kind of question, because there are so many variables,” says Byers. “You don’t get 100 percent yield when you manufacture these discs. We can talk about the materials that produce a good disc, but it also has to do with the manufacturing process. So, just to say the materials to look for doesn’t necessarily relate to it being a better disc.” The same is true vice versa.

So how can you know that the media you’re using will last you for the duration, so those archived photos will still be there when you go back to a disc 20 years from now–or more?

For the moment, you can’t. All DVD and CD vendors make vague claims about disc life expectancy being somewhere between 60 and 100 years–when the discs are treated with care and stored properly.

But NIST’s Byers is seeking to change that. At an OSTA meeting in San Francisco this week, Byers is proposing an industry-wide grading system to indicate disc quality.

Byers is motivated by the desire to see a uniform mechanism in place to guide institutions and individuals who’ll be storing data, music, videos, and images for long periods of time. “They need to be confident in their purchasing, so they can plan for their strategies in storing their information,” Byers says. “Long-term storage has different meanings: For some, 30 years might be enough. For others, 50 or 75 years might be archive, or long-term, quality.”

Longevity

Under Byers’s proposal, a series of tests would be developed to determine whether a DVD would last for a given number of years. “If you were to purchase a disc in a store with a grade that indicates it has passed a test to last X number of years, it removes a lot of uncertainty for the consumer, and it can save some expense in premature migration [to a new storage technology], or loss of data because they waited too long [and the disc was no longer playable],” he says.

Although some archivists–both individual and professional–are concerned about whether today’s digital storage mediums will be readable 50 or 100 years from now, Byers believes the bigger concern for users will be when to migrate their data to the next technology, “before the existing technology is obsolete.”

The Disc Rot Myth

Media obsolescence isn’t the only thing people fear after committing a personal library’s worth of data to CDs and DVDs. But some worries–namely, fear of disc rot–are not fully warranted.

Like a bad seed, the myth of disc rot self-perpetuates, cropping up every now and again as a sudden and mortal threat to your copious collection of prerecorded and self-created discs.

The myth was once rooted in fact. It is true that back in the 1980s, with the first generation of prerecorded audio CDs, the edges of the discs were not always sealed properly, which allowed moisture to get into the disc. Replicated, prerecorded discs use aluminum for the reflective layer; when moisture came into contact with the aluminum on prerecorded discs, explains Byers, it in turn oxidized, causing the aluminum to become dull. “That’s where the term ‘rot’ started,” he says.

But that problem was quickly identified and overcome. “The manufacturers learned what was going on, so now the edges of discs are sealed with a lacquer,” according to Byers. Though the problem is typically associated with CDs, Byers notes that the potential for interaction with oxygen is the same with both CD-ROMs and DVD-ROMs.

The so-called rot issue does not apply to recordable discs. For one thing, recordable optical media do not use aluminum; instead, they use silver, and very rarely gold, or a silver-gold alloy, for the reflective layer. “If the silver comes into contact with sulfates [i.e., pollution, or high humidity], it could affect the silver, but the likelihood of that is less than the likelihood of moisture coming into contact with the aluminum on prerecorded discs,” says Byers.

Enduring Myth

The term rot has persisted, however inaccurately, as a means of identifying a plethora of problems with optical discs. “If you get a faulty disc and see a problem that you can visually see, you call it rot, but it could be the way the disc was manufactured,” says Byers. “Or if it was subjected to extreme moisture and that moisture came into contact with the aluminum, it could be that the reflectivity has changed. It’s not really rot, it’s oxidation of aluminum. It should be a rare event on a disc, unless it’s defective.”

Beyond the realm of defective discs, improper handling can cause otherwise good discs to go bad. Since there’s little protection between the label side of a CD and the data layer itself, “scratches on the label side can scratch the metal, and that will ruin the data,” says Byers. It’s not an issue for DVDs, though, since the dye layer is sandwiched between two plastic layers.

Byers observed a similar problem occurring with press-on labels: “For long-term storage, we recommend not using press-on labels on CDs; when these start to dry up, they can peel the metal right up, damaging data.”

• 0 Comments

Windows XP has a vast number of configuration dialogs, but some adjustments can be performed only by directly editing the Registry. Frequently, tips involving Registry tweaks include stern warnings to back up the Registry before making any change. The Windows XP Backup applet can back up the Registry along with other elements of the System State, but the resulting data file can occupy hundreds of megabytes. You’re better off saving a system restore point each time you’re about to edit the Registry. Better still, you can use Regedit to back up only the Registry keys that will be changed.

Click on Start | Run and enter Regedit to launch the Registry editor. To back up an individual key you plan to edit, navigate to the key and right-click on it. Choose Export from the menu, and save the key to a REG file. Open the REG file in Notepad and insert a few comment lines that describe the source and purpose of the tweak. (To create a comment line, simply put a semicolon at the start of the line.)

Now go ahead and make all the changes to Registry keys and values specified by the tip you’re applying. Any time you add a new key or value, make a note of it with another comment line in the REG file. When you’re done, save the REG file and close Notepad.

If later you want to undo this Registry tweak, just double-click on the REG file and confirm that you want to add it to the Registry. This will restore any deleted keys or values and will restore the original data for any values whose data was changed. Note that this will not remove new keys or values that were added; that’s why you need to make comments about such changes.

Right-click on the REG file and choose Edit, which will open it in Notepad. Check for comments about keys or values that were added, and if you find any, use Regedit to delete them. You can delete the REG file itself once you’ve completed this process

• 0 Comments

Actions are automatically saved to the Actions Palette folder in the Adobe Photoshop or Adobe ImageReady CS Settings folder. If this file is lost or removed, the actions you created are lost. You can save your actions to a separate actions file so that you can recover them if necessary. You can also load a variety of action sets that are shipped with Photoshop.

Note: The default location of the Adobe Photoshop CS Settings folder varies by operating system. Use your operating system’s Find command to locate this folder.

To save a set of actions:

1. Select a set.
2. Choose Save Actions from the Actions palette menu.
3. Type a name for the set, choose a location, and click Save.

You can save the set anywhere. However, if you place the file in the Presets/Photoshop Actions folder inside the Photoshop program folder, the set will appear at the bottom of the Actions palette menu after you restart the application.

Press Ctrl+Alt (Windows) or Command+Option (Mac OS) when you choose the Save Actions command to save the actions in a text file. You can use this file to review or print the contents of an action. However, you can’t reload the text file back into Photoshop.

To load a set of actions:

Do one of the following:
* Choose Load Actions from the Actions palette menu. Locate and select the action set file, and then click Load. (In Windows, Photoshop action set files have the extension .atn.)
* Select an action set from the bottom of the Actions palette menu.

To restore actions to the default set:

1. Choose Reset Actions from the Actions palette menu.
2. Click OK to replace the current actions in the Actions palette with the default set, or click Append to add the set of default actions to the current actions in the Actions palette.

• 0 Comments

Installing Apache on Windows, why? Because let’s face it Windows is easy, and well Apache sure beats using IIS. This tutorial is meant for the person who would like to set up there own little web server. It’s not meant for the IT Person running a fortune 500 company. But hey if you want go ahead.

Instalation:

First thing you need is to download the webserver. Now for windows
users your gonna want to go download the .exe . The apache website is www.apache.org Your gonna wanna head to the apache
binaries sections for Win32 I believe it is at http://www.apache.org/dist/httpd/binaries/win32/
There you will be able to download a version of apache.

Now before you download it you gonna want to make a folder. This folder is
where your gonna server your root directory. Now if you don’t want to do
this it’s ok. You can use the default path if you want. Put usually this helps
in setting up other things like php, and MySQL. Most people do is they create
a folder in the C:\ directory called WWW or somthin. You can name it whatever you want.

Ok so have downloaded the Apache Web Server. Your ready to go with the setup.
No the version I have downloaded was apache_2.0.36-win32-x86-no_ssl.msi This
was a newer version and supposedly supposed to be more secure. The first screen you get when your in the setup is The welcome screen we don’t care much about that
but owell so hit next. The next screen is the terms and service. And yes
your going to agree to the terms duh. The next screen is some documentation.
I never really read it but if you want go ahead and do it. Once your done
hit next again. Know we see a screen that says enter a network domain. Erase what is ever in there and type localhost. Now the next box says
Servername, erace what is ever in the box and put in localhost.
The next is Administrators e-mail address. Go ahead and fill that in.
But make sure to change it. Now there are 2 little radio buttons.
Pick the one that best suites your needs. Now that we got that all
filled out. Hit Next and you’ll go to a screen that asks you which
type of install you want to do. Then hit next.

If you wanted to server out of your one special folder. Change the
file location of were your gonna install apache. Or just leave it at the default path. Click install and it should be on
it’s way. Once it’s done installing hit the finish button.

The test:
First were gonna check to see if Apache installed correctly.
This is how we do it. Open up Internet Explorer and type in ” http://localhost” . If everything went smooth then you should
be seeing a message that looks like this” Seeing this instead of the website you expected?” Yippee!!!
Apache is working. See now wasnt’ that really simple. Ok now were gonna
do some fun stuff.

Alright now that we got or test done lets move on to changing some of this
stuff that apache did on default. In Internet Explorer if you installed
on the deafult path. Make your way to C:\Program Files\Apache Group\Apache2
This is your Main Apache Directory were you can find everything. If you want
take a short break and run around. There are some cool things there. Don’t
worry if you don’t understand what’s in these files just yet.

Break Time:
Go take a leak, get some pepsi and somthin to eat. If you got smokes light
them up in your new found glory.

Alright so now you’ve got apache installed and your about to start dishing out
your web pages that you took so much time on to build. Head to the folder called
htdocs, this is your main folder. There should be a whole bunch of pages What i do
is i select them all and move them to another folder. The htdocs folder is the best
folder in the world. It’s gonna be one of the places you spend most of your time
dishing out content for the world. Ok so get rid of all that stuff that is in your
htdocs folder. And move all your great content inside replacing it. Alright so now
once we moved all are content inside the htdocs folder and we tested it to make
sure it was there. http://localhost remember. Now let’s get out of there. Go to
Apache’s main directory. Now just to be aware of what is going on and get a good
example of how Apache Functions head off to a folder called “conf” This is the
configuration files Apache Uses. If you ever wanted to install php and other
server side scripting languages this is where you would do it. Now you get 2 copys
Use 1 as a backup and never edit it at all. Go ahead and open the folder and open
“httpd.conf” Read it very carefully cause in this tutorial were not gonna read
about it. I just want you to know it’s there. Anytime you edit the httpd.conf file
you must re-start apache in order for it to work. Another good tip for you new people
to apache is you may notice the log files. Yes there great and make sure to make backups
of the logs they will come in handy. As security precautions. I also recommend getting
a firewall set up. There are lots of great security features that apache has but this
is a tutorial to installing apache.

Alright so now you’ve got your webpages up. But the only way people will be able to view
your pages is my typing in your ip address. This is a bumper. Lets look at some free
re-directories. www.n2v.net, This is a cool one. You sign up put your ip adress of your
new webserver in and whalla your done. Type in www. .n2v.net and it goes to your server
and brings up your super nice webpages. Now if you go to google and search for free
domain names or re-directors you should come up with alot. Many People already know
about the www.dot.tk one of the coolest things in the world. Free .tk very simple
That’s all you need. It works perfect for my webserver and I’ve got around 3,000 hits
so it’s working good. If you don’t wanna do it you don’t have to. But it just
makes it simple.

Alright that comes to the conclusion of installing Apache Win32 for WINDOWS users.
Very easy. One last thing Please Read more of the Apache
Documentation either on there website or in your Apache2
directory. If you liked reading this tutorial on how to setup Apache check my
website for others at www.bonfire.tk . Yes there will be follow ups. I’ll be
writing another apache tutorail soon so you can set up PHP. The most awesome
scripting language ever built. And also another on how to secure Apache and yes
ALL FOR WINDOWS!! .

• 0 Comments

First create a new folder somewhere on your hard drive, when you name it hold down “Alt” and press “0160″. This will create an invisible space so it will apper as if it has no name.

Then right click in and select “Properties”, select the tab “custimize” and select “change icon”. Scroll along and you should a few blank spaces. Click on any one and click ok when you hav saved the settings. The folder will be invisible to hide all your personal files.

• 0 Comments

First thing to keep in mind: If your computer hasn’t crashed yet, it will in the future! So instead of waiting for fate to strike, take some precautions now:

1) BACK-UP! Buy some decent DVD-R discs and put everything useful in them. When you have more useful stuff, backup again. Do this often.

2) Keep your computer healthy. Use an antivirus, an anti-spy, and a firewall. Keep them updated. Check regularly for Windows critical fixes.

3) Don’t install software that would do dangerous things to your hard drive. A boot manager would fall in this category.

4) Use a registry cleaner before and after you install or uninstall any software. Many of the problems that will keep Windows from booting are caused by sloppy software that mess up your registry. A good registry cleaner is Tune-up Utilities.
Code:
http://www.tune-up.com/

5) Run chkdsk now and then. Go to Start> Run. Type chkdsk /F. Press enter.

In case your PC has already crashed, read the following:

Most important: Don’t panic! Panic is like a little demon that whispers in your ear to format your hard drive and reinstall everything. Don’t do it! You will lose all your data and the little demon will laugh at you.

To be exact you can still recover your data if you format your drive (by using special software), but only if you don’t write anything on the disc afterwards. In other words format + windows install = bad idea. If you reinstall windows without formating your drive, you will only lose the files on your desktop and “My Documents” folder.

In all occasions you should make sure to safeguard your files before attempting any kind of repair!

So let’s go about how to do that:

The fast way: Go to this site:
Code:
http://www.knoppix.org
. Knoppix is a Linux distribution than runs from a CD. Download the Knoppix ISO and burn it. Put it in your CD drive. On startup access BIOS and change the boot sequence so that your computer boots from the CD drive. Save settings and exit. Upon reboot, Knoppix will load.

Knoppix is much like windows and it comes with its own CD burner. Locate it, launch it and backup everything you want on CD. Now you don’t have to worry anymore!

The less fast way: This requires that you have access to a second PC. Open the case of your computer and remove the hard disk.

Install it as a slave on the second PC.

Depending on respective configurations, you may have to change some jumper settings on the drive. Read the manual for help with installing hard drives and setting jumpers.

After this is done, boot the second PC. If everything went out ok, you should be able to access your drive without problems. (Edit: Note that Win98 cannot recognize a local NTFS (Win2K/XP) disk.)

Copy everything you need from your own hard drive to the other one. Now you don’t have to worry anymore!

Replace your computer’s hard disk, fix all problems and reverse the process to copy the data back to your computer, or take CD backups on the other PC.

• 0 Comments

Masking or anonymizing a Web server involves removing identifying details that intruders could use to detect your OS and Web Port80 Software has developed an IIS server module called ServerMask to combat the majority of issues explored here for the Windows Web Server.

The Server Header Tells All
Most Web servers politely identify themselves and the OS to anyone who asks. Using a network query tool like Sam Spade or this Header Check, you can discern the HTTP Server header. Just request a Web site’s home page and examine the resulting HTTP headers or “banners” sent back by the server. Among them, you will likely find something like this:

Server: Microsoft-IIS/5.0

There is not much mystery here. Apache’s default settings make it no less identifiable:

Server: Apache/2.0.41-dev (UNIX)

You can remove or obscure this HTTP Server header in a variety of ways, depending on your platform. Apache 2.x users who have the mod_headers module loaded can use a simple directive in their httpd.conf file, as follows:
Header set Server “New Server Name Goes Here”

Unfortunately, mod_headers cannot alter the Server header in prior versions of Apache, so 1.3.x users will have to resort to editing the defines in httpd.h and recompiling Apache to get the same result. IIS users can install IISLockDown and use the configuration option in URLScan’s INI file for removing or replacing the header. Be careful with URLScan if you are using Cold Fusion application server — the way the current version replaces the Server header wreaks havoc with CFM pages. In fact, removing the header is the way to go when using URLScan, since if you try replacing the header it moves to the bottom of the header order — which pretty much gives away that you are running URLScan on IIS.

Unsightly File Extensions
Displaying file extensions like .asp or .aspx in a site is a clear indication that you are running a Microsoft server and, in general, hiding file extensions is a good practice to mask the technology generating dynamic pages. You can change your application mappings (.asp becomes .htm or .foo, etc.), but such one-to-one mapping can make mixing server-side technologies painful and does nothing to alleviate headaches during site migrations. Doing without file extensions altogether is an even better idea, not only for security but also for ease-of-migration and content negotiation. Apache people will want to take a look at mod_negotiation. Watch out, though, for the Content-Location header in the server’s response, which can give away the file extension that is not shown in the URL. You might have to suppress this header separately using mod_headers. In a similar vein, Port80 offers a tool called PageXchanger that allows file extension hiding in IIS.

Half-Baked Cookies
The ASP session ID cookie, used by the Session object to maintain client state, is another dead giveaway:

Set-Cookie: ASPSESSIONIDQGQGGWFC=MGMLNKMDENPEOPIJHPOPEPPB;

You can disable ASP Session State so that this cookie is not placed, but you lose the convenience of using the Session object to maintain client state. You could also create an ISAPI filter to change the names of any session ID cookie. On the other hand, ASP sessions are resource intensive, and turning them off improves the performance and scalability of your ASP application, while also helping to anonymize your server.

Send These to the Recycle Bin
WebDAV: Another way of identifying Microsoft servers is their implementation (from Windows 2000 and IIS 5.0 on) of WebDAV — the HTTP Extensions for Distributed Authoring and Versioning. WebDAV itself is not unique to Microsoft or IIS; it is a proposed standard (RFC 2518) with an IETF Working Group. Microsoft’s WebDAV support, however, adds a lot of information to the headers sent back by the server, especially when an HTTP OPTIONS request is made. If you are not using WebDAV (to support Outlook Web Access or Web Folders, etc.), you can disable it entirely by editing the registry or by using IISLockDown and URLScan.

Public Header: Certain Web servers betray their identity by displaying the Public header in HTTP responses. Few popular Web Servers send this header in response to OPTIONS requests (while almost all respond with the similar Allow header). The presence of Public is a good indication you are connected to either an IIS box or Netscape Enterprise 3.6. The Public header can be removed with a custom ISAPI filter (IIS) or NSAPI plug-in (Netscape).

Integrated Windows Authentication: IIS users should not rely on “Integrated Windows Authentication” — especially not as a way of hiding anything on the server. This method betrays the very secret it would keep, since a script or visual hacker can identify the Windows box by means of the WWW-Authenticate headers sent by the server. When a file or directory is protected by NT Challenge-Response authentication, one of the authentication headers contains the string “NTLM” (NT LAN Manager) — a Microsoft-specific form of HTTP authentication.

Get Your Headers Straight
The number and sequence of your HTTP headers and the presence or absence of certain platform-specific headers provide handy ways for more sophisticated hackers to fingerprint your Web server. A relatively unexplored area of server profiling, this will become a more common exploit as administrators start to implement countermeasures against obvious HTTP vulnerabilities like the Server header. For IIS users, a custom ISAPI filter can alter the Microsoft-specific header order or sequence to emulate, say, a default Apache installation. Apache users can accomplish any header order emulation they wish by experimenting with the location and order of Header directives in mod_headers.

Whose Default is That?
Default messages, pages and scripts of all kinds often contain clues to server identity, and these should be removed or modified accordingly. Software behind the Web server often bubbles error messages back through the HTTP request/response cycle, and customized HTTP errors can mask application server, database server, Web server and OS identity. For IIS, CustomError makes it easy for developers to deploy custom 404 and other HTTP error pages. This article shows how to implement custom HTTP errors in Apache. Avoid this on a development server, since, when done properly, it prevents database and server-side scripting errors from being seen — making it tough for developers to debug their applications! Remove or hide any Web or application server administration pages, scripts or documentation installed under your server’s Web root, and make sure to replace those default home pages.

• 1 Comment