mtekk's Crib
February 28th, 2009

When you resort to tactics within the realm malice, are your actions still benevolent? Even Balance should consider this question while working on PunkBuster. While hackers/cheaters are an annoying, when the tools that keep them out operate maliciously the tool maker has gone too far. PunkBuster’s behavior is absolutely uncalled for.

There is absolutely no reason for a legitimate piece of software to download itself from a remote site and reinstall/restart every 15 seconds to 5 minutes. This is how PunkBuster works right now with its PnkBstrA.exe and PnkBstrB.exe services. PnkBstrA.exe will redownload, reinstall, and restart PnkBsterB.exe periodically while in a game “protected” by PunkBuster. If anything goes wrong PnkBstrA.exe will kick the user from a server and give a error in the 13xxxxxx range. PnkBstrB.exe is what actually looks for hackers/cheaters and kicks them. PunkBuster also looks for unknown APIs and will kick you if it finds any, this is the issue it has with Windows 7.

“Why are you playing games on a beta OS?” What’s the point of a beta OS? To test things, that’s the point of beta releases. By playing, or rather try to play, a game I’m testing Windows 7. Since I built a new (for me) computer that is running Windows 7 (64bit), there really is no going back to XP (I do not have Win XP 64bit edition). My gaming is limited to offline games, any Valve title, or Test Drive Unlimited. Basically, anything that doesn’t depend on the horribly broken PunkBuster.

The real shame is that Even Balance has not made any visible effort towards supporting Windows 7. The beta is very solid, a release candidate should be out soon, and at that time the Windows 7 “API” will be “locked” and Punk Buster should be able to be updated to work with Windows 7. If, upon public release of Windows 7, PunkBuster still does not work properly, I’d like to see a someone bring a class action lawsuit against Even Balance for negligence (yes, PunkBuster has angered me to that point).

-John Havlik

[end of transmission, stay tuned]

February 4th, 2009

People are already complaining about the six versions of Windows 7 that Microsoft will release. They should be reminded that Vista had the same number as did XP (Embedded, Starter, Home, Media Center, Tablet PC, Professional, Professional Corporate). The editions are Starter, Home Basic, Home Premium, Professional, Enterprise, and Ultimate.

Windows 7 employees a scheme more like XP originally was, either you’ll use Home Premium or Professional (Professional inherits all the features of Home Premium, unlike Vista Business). In Vista, not all of Home Premium’s features made it into Business edition, which left all users that wanted the Media Center features and Active Directory support with the overpriced Ultimate edition. Windows 7 Ultimate is more or less a non VLK version of Enterprise plus the Media Center features (I suspect the Media Center stuff will not be there in Enterprise despite claims of the contrary by others). End users in developed countries will never see Windows 7 Starter or Home Basic, and in most cases Enterprise.

Here’s a nice decision flow chart for those who are confused (and live in a developed country (e.g.,  USA, Canada, UK, Japan, etc.)):

Windows 7 Edition Selection Guide (for Consumers in Developed Countries)

-John Havlik

[end of transmission, stay tuned]

January 30th, 2009

They say it can not be done. I am here to prove them wrong. That is correct, you can run the Netgear WPN111 USB 802.11b/g card in Windows 7. It’s a little cumbersome, but possible. Here is how you do it. Note that you can leave the USB adapter plugged in during the entire process (that is what I did).

First, grab the latest WPN111 drivers from Netgear’s website. Then, right click and select “Run as administrator”. Continue on through the prompts, when it gets to the point of setting up networks use Task Manager to kill the installer. If you do not kill the installer, the finding networks portion will fail, causing it to automagically uninstall itself.

Now, open up device manager (right click on “Computer” select “Properties” and on the left sidebar click “Device Manage”). Under “Other devices” your WPN111 should show up with a nice warning sign. Select it, and right click, select “Update Driver”. Now select the “Browse my computer for driver software” option. Search in the location “C:\Program Files\NETGEAR\WPN111\Driver” for 32bit Windows and “C:\Program Files (x86)\NETGEAR\WPN111\Driver” for 64bit Windows. Then press “Next” if everything goes correctly, near your clock the WiFi signal icon will show up.

This method was tested on a 64bit install of Windows 7 Beta 1. It should work on 32bit installs as well. Though it seems to work, a few words of advice. First off, do not use WEP, instead use WPA or WPA2. I was unable to get WEP to work on this particular card in Windows 7. Also note a Netgear prompt may show up on startup, do press “Accept” and then tell it you want to use the “XP” wireless manager. If you fail to do this you will have to redo the driver installation.

-John Havlik

[end of transmission, stay tuned]

January 11th, 2009

Like with Vista, I’m beta testing again. This time, I’m using something a little more powerful, my laptop. Since it came with Vista, some direct comparisons can be done. The first thing to note is Windows 7 Beta 1 is just that, a beta. Though I have yet to have something on it crash, there are some visual bugs that need to be worked out. In certain circumstances I am getting visual corruption in Aero. One thing that was improved right off the bat was wireless networking support. Vista was much better than XP, likewise Windows 7 is much better than Vista in this regard.

Booting does not seem much faster than with Vista, but I am using a slightly slower hard drive, and all my ready boost stuff is disabled at the moment. The sound driver that was installed did not work for the built in speakers on my laptop, but installing a Vista driver for it resolved the issue. Like Vista, the automatic installation of drivers is improved greatly over XP. Unlike Vista, in Windows 7 more information about the devise, and process the installer is following is available. Most devices are just plug-n-play with Windows 7, even more so than with Vista.

The window peaking, and new taskbar are two things I’d throw onto the improvement list. On the taskbar you can move around the currently active applications in a manner that reminds me of Avant Window Navigator (OS X is probably like that too). The mouse gestures will take a little bit to get used to and fully learn, so I won’t comment fully on them at this time.

There are still quite a few problems, but hey, it’s a beta so it’s my job to let Microsoft know about them. The first issues is FTP support, it sucks. Vista FTP support wasn’t much better than XP, they both have issues if you double click on an file (they both try to open the files in Internet Explorer). In Windows 7 Beta 1 I can not even log into my FTP folder, all authenticated FTP accesses fail with the error “The handle is invalid.”

Printer drivers for older USB devices do not exist. My HP Officejet v40 (which is built better than most new printers) had drivers built in to Windows since XP. In Vista the included drivers were slow and made printing painfull, in Windows 7 the drivers are not there. HP does not even distribute Vista drivers for the Officejet v40, so unless you have Vista and rip the drivers out of it, or are resourceful with Google, you are SOL.

There are some screen corruption issues, where Aero flakes out, or the font does not render properly. The font issue is reproducible, go add a printer, and scroll quickly through the driver listing (not using the scroll wheel but instead the scroll bar). It is a flaw in the rendering of the letter ‘e’, and specifically the horizontal line is too thick (two to three times the thickness it should be). The fact that a screen capture using the Print Screen button captures this points to a rendering issue caused by windows rather than a driver issue. Using the ClearType configuration utility (a quick, six step, which text chunk looks best ‘test’ ) seems to resolve this issue.

The Aero corruption issue may be a graphics driver issue. So far I have not found a method that reliably reproduces the issue. It will some times affect the taskbar, when opening and closing windows, or minimizing and maximizing them. Sometimes it will affect the titlebar of an application.

Overall Windows 7 is shaping up to be a good replacement for Vista and XP. Sure the Beta has some bugs, but then again it’s a beta.

-John Havlik

Page 3 of 3« Previous123