That's because the M-60 is loosely-based off of the MG-42 design (as per "Lock And Load with R. Lee Ermey").  In fact, the only thing the U.S. military did was lower the rate-of-fire (to help keep barrel changes down- the 42 was notorious for making barrels almost white-hot due to its incredibly high rate-of-fire) as well as some other cosmetic (and not-quite-so cosmetic) changes meant for a modern battlefield. 

Speaking as a person who works in the film biz as an special effects technician (pyrotechnic/mechanical/environmental FX), if there's an overabundance of F/X of ANY sort, it's of the CG kind.  It's all over the place, and it's often used as a crutch instead of a tool like any other tool at a filmmaker's toolbox.  It's often so overused that it takes away from the "gee-whiz!!!" factor that is supposed to be a big part of movies, as practically everything can be written off as being done on computer, which -in the end- will often times ruin the overall impact of a given production. 

This was the case with "2012", which was so over-the-top with CG destruction of whole towns that it literally turned off audiences who yawned and went for their cell phones as a result (at least as I noticed when I saw the film at my local theater).  You could hear people write off various events as "totally done by CG" and other punchline-spoiling remarks that totally defeated the point of the film- to leave you on the edge of your seat. 

Of course, I'm not a fan of CG effects mostly because it horns in on MY work, which has gradually been whittled away from me the last decade-and-a-half.  Creating whole city skylines that fold up over themselves (a la "Inception") is one thing, but leave the real-time explosions and shoot-em-ups to me... it's what I spent almost half my life training for.  

And yes- you CAN tell the difference between real-time (nowadays called "practical" effects) and CG effects, as the CG stuff usually doesn't usually conform to the laws of physics and thermodynamics that guys like me have to keep in mind with doing stuff, even with the numerous physics plug-ins available for MAYA or any of the other software packages they use.  

If nothing else, it's like what a former-mentor of mine told me once with regard to films- "too much of anything is not good".  The same thing can be said about CG effects or anything else for that matter. 

The deleted files totally bypassed the Recycle Bin, making them pretty much unrecoverable, short of using file-searching recovery software (and even THAT was a crapshoot as I found out).  

Quote - Oi, that is nasty! Must check if I have it among all the freebies I've yet to install. I did pick up a few from Rotica and something to make Vicky/Mike look like they've been swimming without tons of postwork would certainly have tempted me.Good thing I didn't use/need it right away.

Is it only Poser 8 this thing's been nuking? If so, good thing I also haven't upgraded yet.

It would appear that the malicious script will attack whatever is the dominant version of Poser you're using.  In my case, I just happened to P8 installed, which essentially put it on the proverbial chopping block as far as that script was concerned.  Since Poser 7 also makes use of Python code, it'd be quite logical to think that it could be a target as well.  

And yes- Smith Micro needs to change how it works with Python code so that it operates in a shell or "sandbox".  Either that, or they should adopt a whole other language all-together... one that doesn't make direct access to memory and -as such- results in decreased security. 

@Trekkie-

"V4WetCreator" was a kind of MAT pose thing that put a "wet" sheen on V4, like what would happen if you went out swimming or something similar.  It was supposed to go over whatever normal textures you already had over your figure and was even had differing levels of wetness including a setting called "Drenched".  The original author of the MAT pose was someone going by the name "Mackie Messer" and it (according to the readme file I found) was copyrighted in 2008.  

If that ZIP file is still out there in the wild, then it should be avoided at all costs. 

So V4WET.ZIP is the file, is it?  I'll go through my archive of stuff and see if I can find it. 

And yeah- that Hermann dude was causing some major trouble and trolling a couple of sites.  He had also been banned from RaunchyMinds (where I Moderate) for assaulting other members as well.  I kind of figured he had something to do with the spreading of that malicious code.

Thanks for the heads up with that ZIP file, nruddock.  

Not sure, as it was a little while ago.  I'm fairly sure I didn't get it here, though. 

The only thing I DO know is it'll definitely ruin your day.  Like I said, I ended up doing the Matlock thing and tried for a second attempt at using it after a reinstall- it totally went through and borked my Poser 8 install.

The GOOD news is that-

• it won't go after any other Runtime libraries you might have connected to Poser 8
• it won't go after any UI preferences you may have set up
• and it won't tinker with your registry and screw with any registration codes you may have present there. 

But that's all small potatoes compared to what it DOES do, which isn't pretty.  

Got a status report-

It turned out that it wasn't a hard drive giving me trouble but rather a problematic Poser item I had installed in my Runtimes.  More specifically, something called "V4WetCreator" is the item in question- it's a texture package that uses Python code to initialize changes to textures.  This would be fine, except for that what it actually does is go through and delete all files and folders in your Poser Runtime until you're left with the "Fatal Runtime Error" pop-up.  

And I know it's the problem because I got curious and tried it again after reinstalling Poser.  

So please- be very weary of "V4WetCreator". 

Well... I'm in the middle of doing a chkdsk on the drive in question, so I hope that isn't the case.  

Sucks to hear about your situation.

About the law getting involved-

You should probably file an identity theft report with the cops as it pertains to the troublemaker.  After all, if he's gonna go after you for assault-and-battery, then you should return the favor for his defiling your online identity the way he did.  Quid pro quo, I always say.  

And make sure homeboy didn't do anything else while masquerading as you... like ordering up a buttload of monkey porn on Amazon.com or something. 

I'll be one of the dissenters of the group and say that you should wait until it's finally ready for primetime.  I bought Poser 8 and got about a day or two of use out of it before it decided to stop working- all it would do is give me these protection fault dialog boxes telling me that "something happened" and that  the program needs "to shut down".  I've followed some of the advice some of the other members here have given to try to rectify the situation (upgrading C++ Runtimes, .NET Runtimes, video card and motherboard drivers, etc.), and it still isn't givin' me any luvin'.

I've also sent the error report text files generated by the protection faults to Smith Micro so they can figure out what the deal is, and I've heard nothing as of yet. 

So yeah- I'd wait at least until there's at least one service release out there before I'd go out and get Poser 8. 

I'll say I've got troubles with my libraries... I can't even get to them in the first place!  LOL

For some reason, Poser 8 has up and decided to stop working on me- all it does is gimme some dialog box saying that "something happened" and the proggie "needs to close".   I'm still at a loss as to what's goin' on there, too. 

I'm kind of having the same trouble in that I was getting crashes as well.  Even worse is the fact that the crashes now happen right off the bat now, immediately after trying to start it up.  So- needless to say- I can't just uncheck "use OpenGL hardware" in the program.  LOL

I'm using an Nvidia card (7950 GT) as well.  

Yeah?  Never heard of that one.  How would I go about checking for that?  And -more importantly- how do I go about making sure it doesn't happen again?  

Yeah.  It's the lame dialog box that pops up whenever a program takes a dump.  Of course, whenever I try to find out some specifics, it won't let me copy any of the hexadecimal error codes to a text file.  That would be needed to send to Smith Micro so they can decipher why their newly-released program isn't ready for prime-time, you know? 

And before anyone asks, I DID install the hotfix that was released days after Poser 8 was supposedly ready to ship, too.