jcl

The colon in the error in odd. Have you tried sprinkling prints in the script to see if it's running?

System control panel, Advanced tab, Environment Variables button. Should take effect immediately.

The only reason I've been paying attention to CES is the Core Duo laptops. Impressive enough for me. (On a completely unrelated note, I just noticed the Pentium 4 is the 80f86.)

It has to be intentional, they would have run it by their lawyers before they posted it. The name could be a coincidence, or they could be different versions of the same license, or it could be a modified license like the GPL+linking license. Weird in any case. The Redmond Reality Distortion Field. I'm familiar with it. Lots but none you can fix

Ah. Not the same samples. Egads. That's not the real MS-PL. It looks like the MS-LPL with the clauses in Section 3 reordered.

The MS-PL and -CL don't have the platform limitation. Where does it say that the code is under the MS-LPL or LCL? The samples I looked at didn't seem to include a license.

The Gaim site has descriptions of some protocols. You might be better off grabbing one or two FOSS IM clients and RingTFS.

Well that's certainly not misleading. The only difference between the SANS recommendation and the MS recommendation is that the former recommends using the patch despite, AFAICT, having no evidence that the patch is beneficial if the DLL has been unregistered, or indeed that the patch isn't potentially malificial. Both solutions disable features and may be only partially effective. AFAICT this a difficult problem. The exploit is taking advantage of an intentional, documented, and used feature of GDI. The simple solutions (e.g. the third-party patch) break compatibility. It's quite possible th

Americans have been saying that since the Constitution was adopted. The US is perpetually on the verge of tyranny. It's one of our cultural neuroses.

Chapter 5 of the Handbook. 5.7.1 in particular.

Multireply. SICP and CTM are highly recommended. SICP may be a better introductory text. Visual Basic is both a programming language and an integrated development environment (IDE) for that language. Very. You need a language that's useful for learning how to program. C++ is not that language. Worry about it when you're working in a domain in which it is useful.

Ack. I just remembered what a pain QEMU was on Windows the last time I tried it. It only ran within a MinGW/MSYS session and networking didn't work. I ended up using VMware Player because it was easier to munge Player configs.

Better performance.

AFAIK you can install whatever you want on it. Grab the player and one of the sample images, edit the config file for the image to point at your install media (I've only used ISO images, but I think it can coaxed into reading a drive), and install over the sample system. I used a Syllable image to test Syllable, ReactOS, FreeDOS, Debian, Fedora, (I think) Ubuntu, Solaris, and a couple other systems.

VMware Player is free. It's not as featureful as the commercial products but it's done everything I've needed. Anyway, Bochs should be fine if performance isn't an issue. QEMU is also worth a look.

Marsh has been posting steadily at G4. At least twice today.

Should be gzip -cd, no? Or gunzip -c or zcat.

The project started in earnest in '98. It's slowly approaching compatibility with WinNT 4.0 with a bit of W2k and WinXP thrown in. Application compatibility seems to be fairly good considering its current state and there's some support for NT drivers.

ReactOS is a reimplementation of Windows NT. Not related to Linux.

Looks like his last posts at G4 were on Nov. 14th.

You can do a lot with 512 bytes. The partition table is only 64 bytes. 512 bytes = 512 octets = 4096 bits. Edit: To clarify, the partition table consists of four 16 byte entries, one for each primary partition. Each entry has six fields describing the partition. Here's an example, with the fields labelled: Active CHS start Type CHS end First sector Length 00 010100 82 fe3f79 3f000000 bbe71d00 80 00017a 83 feffff fae71d00 3df7c604 00 000000 00 000000 00000000 00000000 00 feffff 85 feffff 37dfe404 8a581409 Active is 0x80 if the partition is active (boota

Probably. Yup.

Altering the partition table doesn't affect the partitions. The MBR partition table only contains the information required to identify the partitions: the starting and ending sectors and blocks, the sizes of the partitions, the partition types, and flags that indicate whether the partition is active. Everything else is stored in tables within each partition. As you said, in practice blowing away the partition table will blow away the partitions, but if you restore the table everything will be as you left it.

The MBR contains the partition table. Yup.

Yup.