* Asus N61JQ Owners Lounge *

[doubleatheman]

You people are crazy... I'm lucky to hit 40 per min... but that's all the faster my brain seems to go... lol

[GluttonyH]

Well, I can type over 100 wpm and I haven't had any problems with key skipping .

Sweet. Thanks much for letting us all know that the keyboard doesn't skip. It was the last little thing I needed to know before buying.

[ryalnos]

Just to make sure, I went to typerA.tk:

Your score: 538 keys per minute ~ 107 words per minute

Mistakes: don't(Don't), aCross(Across), know(know,).

None due to skipped letters!

[stevedogg]

Does anyone else use their N61 for any type of photo editing? I bought the new Paintshop Photo Pro X3 and every time I start to edit a photo I am getting c++ runtime errors and it shuts down.

Is that program better than gimp? I am not a serious photo editor, but gimp is really powerful (basically a free Photoshop rival).

[stevedogg]

Thanks Donald, that is good to know, because it confused the hell out of me.

You'll be confused again when OLED displays are mainstream . As Donald stated, these "LED" displays only use LEDs for backlighting (white LEDs). The white light is filtered into red, green, and blue, which are then individually and electronically attenuated using liquid crystals. This is why the black on your ASUS doesn't look so black (the crystals are unable to block all of the backlighting). OLED displays found on some phones have pixels composed of individual (organic) LEDs which are each red, green, and blue. There is no filtering involved, and the pixels can be turned off. Such displays have perfect blacks and use less power when darker images are shown on the screen.

[Jgoble25]

Is that program better than gimp? I am not a serious photo editor, but gimp is really powerful (basically a free Photoshop rival).

I don't know about better, but easier for me yeah. I just wish I could use it on here.

[stevedogg]

I don't know about better, but easier for me yeah. I just wish I could use it on here.

The Visual C++ runtime library is basically an external library (DLL or dynamically linked library) containing code required by your software to run. Since it is external, it's possible that updating the library will fix your problem. It is kind of a long shot but worth a try. It won't do any harm to install the latest versions on your computer. There are basically 4 flavors: 2005 and 2008 versions, each of which can be 32-bit or 64-bit (many programs running on your 64-bit Windows OS are actually 32-bit programs that use 32-bit libraries).

Install these 4 and try the software again:

Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)

Microsoft Visual C++ 2005 SP1 Redistributable Package (x64)

Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)

Microsoft Visual C++ 2008 SP1 Redistributable Package (x64)

Like I said, it is a long shot. Hope it works for you.

Edit: Even if you install the above libraries, there is still a chance that they may not get used by your application. This can happen in poorly-built apps that copy the runtime libraries to the local application directory. Outdated or incompatible versions may be used instead of the newer ones installed in your Windows winsxs directory. If you suspect this, you can browse through your Paint Shop application directory and delete the files. They have names like msvcr80.dll.

[LordDavon]

You'll be confused again when OLED displays are mainstream . As Donald stated, these "LED" displays only use LEDs for backlighting (white LEDs). The white light is filtered into red, green, and blue, which are then individually and electronically attenuated using liquid crystals. This is why the black on your ASUS doesn't look so black (the crystals are unable to block all of the backlighting). OLED displays found on some phones have pixels composed of individual (organic) LEDs which are each red, green, and blue. There is no filtering involved, and the pixels can be turned off. Such displays have perfect blacks and use less power when darker images are shown on the screen.

Oh, but I do love the OLED screen of my Samsung Moment!

[Sm0k3d 0uT]

Although it does happen here, it is minimal in this place. This is the one place I feel that people can understand the frustration.

David I have downloaded andLinux and eagerly awiting installing it. I think the idea behind it is great. Not having to have a second partition to run Linux or worrying over a LiveCD is the answer I was looking for.

And for all those haters you encounter complaining about no 64bit edition, just tell them to load up a Virtual Machine with a 32 bit OS. That's what I will do till a 64bit version is available.

[LordDavon]

David I have downloaded andLinux and eagerly awiting installing it. I think the idea behind it is great. Not having to have a second partition to run Linux or worrying over a LiveCD is the answer I was looking for.

And for all those haters you encounter complaining about no 64bit edition, just tell them to load up a Virtual Machine with a 32 bit OS. That's what I will do till a 64bit version is available.

Thanks. I can't believe that andLinux just turned 5 years old. It is wild how much work I have done for free. HA!

I actually sold one of my slower 64bit machines to get the N61 so I can work on porting andlinux to x64. I am going to do this in phases.

There are 5 major parts of andLinux. The linux.sys driver, WinTap (network communication), the Linux Kernel, the OS (and all of the modules) and the communication portals between Linux and Windows.

The linux.sys driver allows Linux and Windows to co-exists in Windows. Also, the WinTap driver allows for the Linux system to use networking. I HOPE these can safely be recompiled (as I think they are already 64bit safe) to allow for the 32bit version of andLinux to run on a 64bit OS.

The trick comes in porting the a 64bit Linux kernel to a 64bit Windows application. Here is about the highest level explaination I can come up with: Linux handles long integers (really big whole numbers) as 8bit where Windows handles them as 4bit. Because of this, when you cast (think of it as converting) a pointer (think of this as something specifying an exact memory location), they can't be cast properly between Linux (8bit) and Windows (4bit) and is unsafe (think of this as CRASH|BSOD|BIG!NO!NO). So, CoLinux (a port of the Linux kernel to Windows that andLinux uses) needs a complete rewrite of how it handles memory. As well, x64 Windows is more protected then 32bit Windows so, there is no telling what else we are going to encounter when porting things over.

This is a pretty big job but, I am not alone. Henry Nestler (the main CoLinux developer) has already made great strides in this work. As well, I have a few very talented C coders at my disposal. My C skills are pretty limited since I have been living in C# and Java for the past few years.

Anyway, I am installing a 64bit version of Ubuntu on the N61 this weekend so I can start porting things over. I just hope I don't screw up the N61 in the process. I may use the HP TX2 for testing since I am a bit nervous about screwing up the N61.