Meet you back here in half an hour.
What are you going to do?
What I always do - stay out of trouble... Badly.

Friday, February 10


There Is Probably Someone Out There

Who can use this information, so here it is.

If you were developing a Neverwinter Nights module, and then your computer violently exploded because, for example, you were running Windows ME with 768MB of memory, and then you installed Neverwinter Nights on your new computer and discovered to your delight that you had a recent backup of your work and then discovered to your dismay that when you try to load it into the NWN toolset it comes up with the error "The specified file could not be found", it's probably just because you installed NWN in a different directory and somewhere it's hardcoded the filepath and refuses to read the file even though the file is right there dammit and in fact the only reason it can't read the file is because it just did read the file, then the solution is ModPacker.

Use ModUnpacker to unpack your module; use ModPacker to pack it again; drop the resulting module back in your modules directory; and it will work.

Posted by: Pixy Misa at 08:23 AM | Comments (1) | Add Comment | Trackbacks (Suck)
Post contains 181 words, total size 1 kb.

Thursday, February 09


Thought For The Day

An ounce of undo is equal to a pound of "Are you sure?"

Posted by: Pixy Misa at 09:30 PM | No Comments | Add Comment | Trackbacks (Suck)
Post contains 21 words, total size 1 kb.


Windows (Net) Working

There is an answer.

The secret is that my notebook has not three, but four network connections. (Not counting the modem.) Ethernet, WiFi, Wireless Broadband - and FireWire. And FireWire does not get disconnected when it gets, uh, disconnected.

Given this, the solution is obvious. Simply bridge the ethernet, WiFi, and FireWire ports. VMWare will then automatically bridge to the bridge, and all your computers, virtual and otherwise, will be able to talk just they way they would if Windows wasn't getting in the way in the first place.


Except for the part where your wireless network no longer works. So you can either have your computer able to talk to itself, or you can have it able to talk to the rest of the world. Okay, so all you need to do is take WiFi out of the bridge and then disable the bridge.


If I got WiFi at work, that would work all the time. I think. Must seek cheap WiFi access points...

Update: Or I can just toggle the bridge on and off. Off when I'm on WiFi, on when I'm on ethernet or mobile. Wups. That doesn't work either. Oh, yeah, they have to have the same IP address. Tweak tweak... Shut up, Windows, I know what I'm doing. Ah. Good. Nope. Now I don't have internet access. What if I disable FireWire as well? Right, now it works. Windows, you suck.

Posted by: Pixy Misa at 04:53 AM | Comments (2) | Add Comment | Trackbacks (Suck)
Post contains 244 words, total size 1 kb.

Wednesday, February 08



I decided to install Kdevelop on Amelix, because I'm planning to use Amelix for developing M*nx and I've heard good things about Kdevelop. So I went into the software manager and told it to download Kdevelop, which is only a 30MB package. No problem.

Except that to install Kdevelop I need to install 550MB of other packages and libraries first. When I already have a 2.8GB install, including the full GCC compiler suite. It does this all for me automatically, but still...

I ended up having to move the whole of /opt onto my new 20GB drive, because I was almost out of space on /.

Posted by: Pixy Misa at 09:01 PM | Comments (5) | Add Comment | Trackbacks (Suck)
Post contains 108 words, total size 1 kb.


Instant Disk Space

The other problem I had was that the SUSE installation I'm using (available here, more Linux installs here) only had 4GB of disk. 400MB is allocated to swap, leaving 3.6GB for files. A full Linux installation these days uses up... more than 4GB.

A slight problem, and the main reason why I really really needed to have the networking working. But then I decided to try renaming the virtual machine, because it was called "KDE_3.5_on_SUSE_Linux_10", which is a bit of a mouthful. I renamed it to Amelix, because its Linux running on Amelia (the name of my notebook).

Only it didn't work, because it was looking for the old file name. So I took a look at the config file, and lo! It is text. And I could change the name of the file therein, it it did work.

And what's more, it defined the virtual disk as SCSI drive 0:0. So I wondered, what would happen if I cloned the virtual disk file, and edited the config to point SCSI drive 0:1 at the new virtual disk.

The answer: It works. So I can add as many 4GB disks as I want... Until I run out of real disk, anyway.

Posted by: Pixy Misa at 01:17 AM | Comments (11) | Add Comment | Trackbacks (Suck)
Post contains 207 words, total size 1 kb.

Tuesday, February 07


Virtual Private Crap

Okay, a little explanation for the previous entry. Or details, anyway, since anyone who has ever tried to use Windows networking would agree with the general concept.

Thanks to Eric's recommendation, I have installed VMWare Player on my notebook. A couple of hours after installing this, I had a full version of SUSE Linux with KDE 3.5 up and running. It's fast and it's free, and it gets me away from all the nasty little gribbles that have been plaguing me when it comes to doing development work on Windows.

Except for networking.

It's on my notebook, as I mentioned. At work, I plug the notebook into a spare port in the ethernet switch on my desk. At home, I have WiFi. In between, I have wireless internet. So I have three network connections which I use at different times.

I need two things: One, that the virtual machine can connect to Windows on the notebook itself, and two, when I do have a network connection, that the virtual machine can access it.

Here's the problem. When a network connection is disconnected on Windows, Windows can't ping itself on that network port.

This is stupid. It means that Linux running under VMWare can only talk to Windows running on the same machine when I have the network cable plugged in.

VMWare supports a "host only" mode, where the guest operating system can only connect to the host machine (in my case, Linux talking to Windows), but as far as I can see, this suffers from the exact same problem.

It also supports virtual networks, which would satisfy part one, but you can only use them under VMWare Player if the person who set up the guest operating system configured them at the time. And for the copy of SUSE I'm using, they didn't.

So it almost, almost does everything I want, except it doesn't.

Oh, and every time I switch from WiFi to ethernet, I have to spend half an hour fighting with it before it will talk to itself.

Posted by: Pixy Misa at 09:07 PM | Comments (3) | Add Comment | Trackbacks (Suck)
Post contains 346 words, total size 2 kb.


Windows Networking


Back later. Now, where did I put that hammer?

Posted by: Pixy Misa at 07:57 PM | Comments (2) | Add Comment | Trackbacks (Suck)
Post contains 14 words, total size 1 kb.

<< Page 2 of 2 >>
66kb generated in CPU 0.0257, elapsed 0.2146 seconds.
56 queries taking 0.1975 seconds, 375 records returned.
Powered by Minx 1.1.6c-pink.
Using http / / 373