I had the same error message. Do you have a Logitech Quickcam? I found that the Quickcam software which runs in the background on start-up was keeping a lock on the mozMapi32.dll file in the Thunderbird program folder. I had to use process explorer to kill off QuickCam10.exe before I could complete the installation.
I played through all of HL2 on a low end machine with no problems. Then, a few months later, I upgraded my hardware and decided to have a second run through it. I found it almost impossible to play and had to give up pretty early on. It gave me some of the worst headaches I've ever had, and it took a few hours to recover after I stopped playing.
I've just finished HL2:EP1 on the same machine and I'm happy the say the problem has been fixed for me. I did experience a twinge of nausea at a few points, but I think it was just because I'd mentally associated the game with feeling ill. Overall I found it very playable.
As a long time FPS player I find it very strange that HL2 could make me feel so bad. I'd be really interested to find out what caused it.
I couldnt actually get any of them to run on my machine, but they are by the guy who was given credit for finding the hole.
This exploit seems quite similar to the IE5.0 one a few years back. When viewing multipart HTML docs (.mhtml) IE would use the windows temp directory (not the temp internet files dir) to store any parts of the doc that were uuencoded. It was then trivial to access the files in this dir. So you could uuencode your nastyprog.exe and attach it to the end of a HTML doc, then use some activeX scripting or sunnit to run it.
That stuff was all patch a while back, but this new stuff seems to be able to run the code/script without it having to be stored on the disk.
Slashdot Mirror
I had the same error message. Do you have a Logitech Quickcam? I found that the Quickcam software which runs in the background on start-up was keeping a lock on the mozMapi32.dll file in the Thunderbird program folder. I had to use process explorer to kill off QuickCam10.exe before I could complete the installation.
I played through all of HL2 on a low end machine with no problems. Then, a few months later, I upgraded my hardware and decided to have a second run through it. I found it almost impossible to play and had to give up pretty early on. It gave me some of the worst headaches I've ever had, and it took a few hours to recover after I stopped playing.
I've just finished HL2:EP1 on the same machine and I'm happy the say the problem has been fixed for me. I did experience a twinge of nausea at a few points, but I think it was just because I'd mentally associated the game with feeling ill. Overall I found it very playable.
As a long time FPS player I find it very strange that HL2 could make me feel so bad. I'd be really interested to find out what caused it.
You might be thinking of Peep http://developers.slashdot.org/article.pl?sid=00/1 2/10/1529249&mode=nested
I dont know the exact details but the example exploits produced by the finder of this hole used
audio/x-wav
Although I am sure there are probably many more you could use
Heres a link to some demos of the exploit. (Just check out the source to see how they work)
http://www.kriptopolis.com/cua/eml.html
I couldnt actually get any of them to run on my machine, but they are by the guy who was given credit for finding the hole.
This exploit seems quite similar to the IE5.0 one a few years back. When viewing multipart HTML docs (.mhtml) IE would use the windows temp directory (not the temp internet files dir) to store any parts of the doc that were uuencoded. It was then trivial to access the files in this dir. So you could uuencode your nastyprog.exe and attach it to the end of a HTML doc, then use some activeX scripting or sunnit to run it.
That stuff was all patch a while back, but this new stuff seems to be able to run the code/script without it having to be stored on the disk.