Don't even get her started on the thong-bikini babes that the male gunmen win as prizes in 'Grand Theft Auto,' which was sent to stores with hidden sex scenes left embedded on the discs by programmers.
There is a funny rant about this in today's sfgate.com (There's Sex In My Violence!
What's this lame soft-core porn doing in my ultraviolent "Grand Theft Auto"? I am outraged!).
Obviously what is needed is a method for dual encrypted files. Basically an encryption/steganography combo. When unencrypted with the 'fake' key, you just get whatever text you encrypted with that key - something uninteresting like expired credit card numbers or letters to grandma and it looks like you have complied with the order. Meanwhile the real key unlocks the data you want to keep secret.
Naturally the algorithms would require that it would be undetectable that this is what you have done.
Some alarm systems have something similar. When you open the business you use the real code. When the robber forces you to open up at gunpoint you use the fake code. The alarm does turn off as expected but it also calls the police with an "under duress" alarm.
And to make matters worse, failures tend to occur more often when things are heavily loaded - ie. not in the wee hours but rather when people actually want to use the phone.
Obviously someone has a different definition of "not bad" than I do.
I remember when M$ proudly claimed 99.9% uptime for NT. To me that sounded terrible. Over 3.5 FULL 24 HOUR DAYS of downtime every year. Horrid!
Saving, borrowing, and going in together with my roommate to put together the $2,000 (that was lots more then than it is now) to buy an IBM PC. The beast came complete with no drives (that's right, NONE - we wrote things via the embedded "cassette-basic" and could save the programs to a cassette tape recorder), 16kB RAM and a monochrome non-graphical display.
The San Francisco computer shows of the early 80s. Those were fun shows. I saw the Osborne I when it was first shown there and went on buying sprees to buy chips (yes, young-ones, individual chips) to plug in and get my RAM up to 64kB, as well as expansion cards (everything was optional back then) to get a clock, printer port, serial port, and finally 640kB of RAM (expansion card and lots and lots of chips to plug in). Everything was outrageously expensive by today's standards so there were lots of cobbled together add-ons. A favorite was a photocell gizmo that clipped onto the print-head of an Epson dot-matrix printer which along with some software made it work as a scanner.
I remember buying DOS 1.0 and a third-party 320k double-sided floppy drive (IBM was only shipping 160 single-sided drives at the time). You had to patch DOS to get it to use both sides of the disk and at $15 for a floppy this was important. The alternative was to buy one of those punches that cut a notch in the opposite side of the disk so you could flip it over and use it as two single-sided floppy disks. When we went to add a second drive we had to figure out how they had wired the drives and found out that all OEM drives were jumpered as "drive b" and the cable between the two was twisted to swap the first and second drive signals. We cut the jumpers and got everything working.
Later, we bought a modem (Cermatek 300/1200: $600) and had to convince the powers that be at UC Berkeley to upgrade the modem bank. The head of the computer-center finally told me that they were now buying 1200 BPS modems because they were the "wave of the future".
I remember having lots of aha's about how computers really work when we learned assembly on DEC computers. The first assignments required us to toggle in the programs at the front-panel of PDP-8 machines. Octal was great for that because the PDP had the switches grouped in threes so you got really fast at using the middle three fingers to toggle in the octal instructions.
Finally, I remember a little cardboard computer we used in one class. I still have it somewhere but can't remember the its name. It had sliders for the registers, a card with small holes for memory registers and little "bugs" to use as a memory and instruction pointers. You filled in the memory cells and registers in pencil and "executed" the "programs" manually by erasing and rewriting memory, sliding the register stack sliders, etc. One day I'll photograph it and put it up on the web.
This sounds hauntingly familiar. In the first disaster NASA had simply gotten used to seeing some burn-through on the o-rings to the point that it was "normal", in the second disaster they had seen foam and ice come off the orbiter but nothing bad had happened so far.
In the third disaster they couldn't find the cause of the fuel sensor problem so they declared that only three were needed and launched anyway.
Bob Cowell writes an excellent column in Computer magazine. In one column titled "Murphy Was Wrong" he points out that unlike Murphy's Law, things usually go right in spite of a myriad of glitches. In fact, they go right so often that people start ignoring the warning signs. It usually takes a severe or multiple failures to cause an actual catastrophe.
If something is failing it is failing for a reason. Don't launch till you know the cause and for gods sake don't "solve" the problem by simply rewriting the rules to say that it's OK for a "critical" system to fail.
As cool as the space exploration and the shuttle are, it may be time to say that the program has utterly failed to meet its goals, will never be able to meet its goals, and that we should cut our losses, take the information we have learned from the shuttle program, and move forward on a replacement.
Consider that the stated goal for the shuttles was 100 missions each. Unfortunately that's pretty close to the tally for the whole fleet. Oh, and there is that little annoying fact that 40% of the orbiters have crashed killing all aboard.
All the necessary info is in zoneinfo or tz files. Look in/usr/share/zoneinfo on Linux for the compiled timezone files. Your local zone is just the appropriate file copied or linked to/etc/localtime.
Substituting new zoneinfo files should be all that is needed for apps that rely on the system timezone stuff.
I'm sure that the change will be in a monthly update from M$ so Windoze should also be OK as long as people update ('course the update requirement goes for *nix as well...)
Just Google "zoneinfo" and hit "I'm feeling lucky" for plenty more info.
For programs with hardwired code all bets are off.
Good nose. And when the politicians are bought and paid for by Archer Daniels Midland and friends the result is government subsidies for corn-derived ethanol and a full-court press to keep Brazilian ethanol (sugar derived) out of the US (just google brazil ethanol imports).
Forgot to mention - kpilot doesn't seem oriented to printing because it (optionally) acts as an interface to KOrganizer, KAddressbook, etc. so it assumes you will use those as your desktop organizing apps and will print from there.
For a GUI that lets you install to the Palm I've used kpilot and jpilot. There are also plenty of command-line tools that allow you to do backups of the Palm (in fact lots of the GUIs are built on top of the same command-line tools).
My biggest gripe is that none of the tools I've tried is really good at printing. Jpilot is OK but has a few bugs and kpilot doesn't print at all.
Also, some add-on software has corresponding desktop software that is Windoze only but you can generally use it on the Palm only.
As a Dr. have you ever used epocrates for the Palm. It's a pretty cool app for drug referencing (at least it seems cool to me, a non Dr.)
Certain types of research have bias built-in. If BigDrugCo wants research results on NewExpensiveDrug they aren't going to farm the research to the people who told them their last drugs were worthless. Therefore, if I want BigDrugCo's $$$ in the future I'll try to design the study and present the results in the most positive way. Whether or not I'm aware of it there will be some underlying pressure.
As such, I feel that this type of study needs what I've coined a "triple-blind study" in which a neutral party is placed between the funder and the researcher.
This neutral party would then choose researcher(s) at random from a pool of candidates qualified to do the research and frame the question in a neutral way. The funding source and desired outcome would be withheld from the researcher.
Re:what the fuck is "guaranty" ?
on
Blank Keyboard
·
· Score: 1
It's a word in the English language. You see, there is this thing called a "dictionary" that allows you to answer this sort of question.
Now technically they probably meant guarantee since guaranty and guarantee are slightly different. Although guaranty can be used for guarantee it more often is used where the agreement is an assurance of financial payment.
As a side note, I used to work for a bond insurance company which, due to mergers, doesn't exist anymore. The company name was "Capital Guaranty" and we were in the Steuart tower of a building in San Francisco. If I didn't spell out everything I would end up getting things sent to one of the many combinations of Capital/Capitol Guaranty/Guarantee in the Steuart/Stuart/Stewart tower...
Worse still was growing up at the (then named) Naval Weapons Center, China Lake. When you get something sent to the Navel Weapons Center it conjures up all sorts of scary images.
I still have my Poqet PC from ~1989. Fujitsu bought them out and while they haven't been made for years, you can still find them on eBay - usually for less than $100.
80x25 screen, MS-DOS, keyboard you can touch-type on, Lotus 1-2-3, etc. It's instant-on and runs for weeks on a pair of AA batteries. It won a 1989 Byte award of distinction.
I suppose a Palm with a folding keyboard might do the trick nowdays but the Poqet was (is) a slick little machine.
Last two times I've lost dialtone it's taken days to get it back up. They simply don't work on the problem after hours 'cause it costs them overtime. The days when the phone company rushes to fix a problem are long gone.
I'd say the main problem with free alternatives is really stupid project names. Moodle? WTF?
At least, unlike some projects, a Google search on "moodle" returns information relevant to the project. It used to be that a simple search for "postfix" returned pages on programming syntax. Now, possibly to the annoyance of those searching for syntax info, almost all the results are for the Postfix mail server.
Apparently geeks make more web pages or Google is biased toward geeks since a single word search on jakarta, ant, apache or forrest returns as the first hit the Apache foundation project page rather than info on Indonesia, insects, native-americans/aircraft, or woodlands.
Corporations spend big bucks on product naming. They need to know if it is copyrighted or trade-marked world-wide, whether it is potentially offensive in any region where they intend to market the product. They run market-research to find how consumers respond to the various names. Most open-source programmers are more interested in the quality of their creation than in spending time or funds on product naming research.
From the Moodle site:
The word Moodle was originally an acronym for
Modular Object-Oriented Dynamic Learning environment, which is mostly useful to programmers and education theorists. It's also a verb that describes the process of lazily meandering through something, doing things as it occurs to you to do them, an enjoyable tinkering that often leads to insight and creativity. As such it applies both to the way Moodle was developed, and to the way a student or teacher might approach studying or teaching an online course. Anyone who uses Moodle is a Moodler.
Admittedly, I don't tend to read volumes of cost comparisons between open-source and proprietary software but one thing I haven't seen in the cost comparisons I have read is the cost of managing licenses. In my experience this is non-trivial.
As you have noted here there is a cost in wasted time dealing with the vendor and probably in down-time for your users who need the software.
Even if the key wasn't lost there is a cost in maintaining the records of keys.
If you can't convince them to provide you with your key then there may be the cost of buying another copy if you decide to continue doing business with the crooks who are currently screwing you.
I have personally spent days with tech-support trying to work around buggy activation schemes. This was not only lost time for me but for the projects that relied on the equipment in question.
I've also had to battle with vendors to get rid of evergreen clauses or to carefully track them when they couldn't be removed.
Then there is the recent issue with certain Adobe software not installing on machines with RAID arrays (you are installing on multiple disks which is prohibited...). Go figure.
And the issue of Intuit not providing keys for old versions of software even though they acknowledge that they have them. Upgrade or kiss your data goodby.
When you add users or machines you need to track your license status, get purchase orders, etc. Renegotiating bulk contracts, watching out for evergreen clauses and such takes legal and management time.
One need only scroll through a few of Ed Foster's "Gripe Line" columns from InfoWorld to see how much pain product activation is causing.
It's a simple web-based logging system (single stand-alone executable availabile for *nix or windoze) that you can get running in just a few minutes. We use it for tracking issues with vendors, entering changes to machines, etc.
It's free and the opportunity cost is only an hour or so. It won't do everything but it will probably meet your needs and you can impress your coworkers by having it up and running by the end of the day.
I'm surprised that the PSU and all the cables (like speaker/CAT5) work at all, I feel so uneducated.
Why wouldn't they? Oil doesn't conduct. That's why it's used for cooling in electrical devices such as transformers, dummy-loads and such. I recall one vendor who demonstrated the high breakdown voltage of their oil by running a TV set in a vat of the stuff. Almost anything has better heat removal ability than air and for silent running it's not a bad idea.
There is still the problem of removing the heat. If there is enough surface area to allow the heat to be removed then you are ok, otherwise the oil (and everything else) will get too hot. Encasing everything in a metal box with fins on the outside would probably keep things even cooler.
last weekend (a friend works for ILM). It is most definitely the best of the recent three. The progression toward the creation of the Empire and the conversion of Anikin to Darth is nicely done and the creation of the Empire bears a scary resemblance to current US politics.
One scene (you'll know it when you see it) was distractingly similar to the Black Night scene in "Holy Grail" and given that this one ends roughly 20 years before Episode IV one can quibble about the age of a couple of the characters. Manikin Skywalker is as wooden as ever but all in all it was a fun time.
The biggest problem was that the early morning line snaked way too close to Starbucks leading many of us to drink way too much of the dark stuff right before a 2.5 hour movie. And when you see movies with the movie-makers _nobody_ leaves before the last credit scrolls off the screen.
step 2) delete all the DLLs and activeX controls from your IE Downoads directory. Many of them will be held 'open' and won't be deletable.
But often you can rename them even when you can't delete them. It's always worth a try. On reboot it can't find the offending file.
Re:Isn't this technically illegal?
on
Hack IIS6 Contest
·
· Score: 1
Read the rules. They clearly state "Contest open to anyone at least 18 years old as of date of entry. Void where prohibited by law." Guess they won't need to buy that Xbox...
Slashdot Mirror
There is a funny rant about this in today's sfgate.com (There's Sex In My Violence! What's this lame soft-core porn doing in my ultraviolent "Grand Theft Auto"? I am outraged!).
dd count= if=/dev/random of=subway_bomb_plans
Obviously what is needed is a method for dual encrypted files. Basically an encryption/steganography combo. When unencrypted with the 'fake' key, you just get whatever text you encrypted with that key - something uninteresting like expired credit card numbers or letters to grandma and it looks like you have complied with the order. Meanwhile the real key unlocks the data you want to keep secret.
Naturally the algorithms would require that it would be undetectable that this is what you have done.
Some alarm systems have something similar. When you open the business you use the real code. When the robber forces you to open up at gunpoint you use the fake code. The alarm does turn off as expected but it also calls the police with an "under duress" alarm.
Those who are curious about the nifty little cardboard illustrative aid to computation can download the emulator.
94.8% is....
20 full days per year down time or
1.2 hours down EVERY DAY!
And to make matters worse, failures tend to occur more often when things are heavily loaded - ie. not in the wee hours but rather when people actually want to use the phone.
Obviously someone has a different definition of "not bad" than I do.
I remember when M$ proudly claimed 99.9% uptime for NT. To me that sounded terrible. Over 3.5 FULL 24 HOUR DAYS of downtime every year. Horrid!
Saving, borrowing, and going in together with my roommate to put together the $2,000 (that was lots more then than it is now) to buy an IBM PC. The beast came complete with no drives (that's right, NONE - we wrote things via the embedded "cassette-basic" and could save the programs to a cassette tape recorder), 16kB RAM and a monochrome non-graphical display.
The San Francisco computer shows of the early 80s. Those were fun shows. I saw the Osborne I when it was first shown there and went on buying sprees to buy chips (yes, young-ones, individual chips) to plug in and get my RAM up to 64kB, as well as expansion cards (everything was optional back then) to get a clock, printer port, serial port, and finally 640kB of RAM (expansion card and lots and lots of chips to plug in). Everything was outrageously expensive by today's standards so there were lots of cobbled together add-ons. A favorite was a photocell gizmo that clipped onto the print-head of an Epson dot-matrix printer which along with some software made it work as a scanner.
I remember buying DOS 1.0 and a third-party 320k double-sided floppy drive (IBM was only shipping 160 single-sided drives at the time). You had to patch DOS to get it to use both sides of the disk and at $15 for a floppy this was important. The alternative was to buy one of those punches that cut a notch in the opposite side of the disk so you could flip it over and use it as two single-sided floppy disks. When we went to add a second drive we had to figure out how they had wired the drives and found out that all OEM drives were jumpered as "drive b" and the cable between the two was twisted to swap the first and second drive signals. We cut the jumpers and got everything working.
Later, we bought a modem (Cermatek 300/1200: $600) and had to convince the powers that be at UC Berkeley to upgrade the modem bank. The head of the computer-center finally told me that they were now buying 1200 BPS modems because they were the "wave of the future".
I remember having lots of aha's about how computers really work when we learned assembly on DEC computers. The first assignments required us to toggle in the programs at the front-panel of PDP-8 machines. Octal was great for that because the PDP had the switches grouped in threes so you got really fast at using the middle three fingers to toggle in the octal instructions.
Finally, I remember a little cardboard computer we used in one class. I still have it somewhere but can't remember the its name. It had sliders for the registers, a card with small holes for memory registers and little "bugs" to use as a memory and instruction pointers. You filled in the memory cells and registers in pencil and "executed" the "programs" manually by erasing and rewriting memory, sliding the register stack sliders, etc. One day I'll photograph it and put it up on the web.
This sounds hauntingly familiar. In the first disaster NASA had simply gotten used to seeing some burn-through on the o-rings to the point that it was "normal", in the second disaster they had seen foam and ice come off the orbiter but nothing bad had happened so far.
In the third disaster they couldn't find the cause of the fuel sensor problem so they declared that only three were needed and launched anyway.
Bob Cowell writes an excellent column in Computer magazine. In one column titled "Murphy Was Wrong" he points out that unlike Murphy's Law, things usually go right in spite of a myriad of glitches. In fact, they go right so often that people start ignoring the warning signs. It usually takes a severe or multiple failures to cause an actual catastrophe.
If something is failing it is failing for a reason. Don't launch till you know the cause and for gods sake don't "solve" the problem by simply rewriting the rules to say that it's OK for a "critical" system to fail.
As cool as the space exploration and the shuttle are, it may be time to say that the program has utterly failed to meet its goals, will never be able to meet its goals, and that we should cut our losses, take the information we have learned from the shuttle program, and move forward on a replacement.
Consider that the stated goal for the shuttles was 100 missions each. Unfortunately that's pretty close to the tally for the whole fleet. Oh, and there is that little annoying fact that 40% of the orbiters have crashed killing all aboard.
All the necessary info is in zoneinfo or tz files. Look in /usr/share/zoneinfo on Linux for the compiled timezone files. Your local zone is just the appropriate file copied or linked to /etc/localtime.
Substituting new zoneinfo files should be all that is needed for apps that rely on the system timezone stuff.
I'm sure that the change will be in a monthly update from M$ so Windoze should also be OK as long as people update ('course the update requirement goes for *nix as well...)
Just Google "zoneinfo" and hit "I'm feeling lucky" for plenty more info.
For programs with hardwired code all bets are off.
My new Palm Tungsten E2 lists the warranty as 90 days but if you are in the EU it is 2 years. What gives?
After a server room AC failure following routine maintenance I went and bought one of these units the next day.
Extremely easy to set up. I just poll it via http with a script and update an rrdtool graph. I generate a pager alert if the temperature is too high.
Next day the AC failed again (on a Friday evening no less) but the pager called me when I was just a couple miles from the office. Disaster averted.
Good nose. And when the politicians are bought and paid for by Archer Daniels Midland and friends the result is government subsidies for corn-derived ethanol and a full-court press to keep Brazilian ethanol (sugar derived) out of the US (just google brazil ethanol imports).
Forgot to mention - kpilot doesn't seem oriented to printing because it (optionally) acts as an interface to KOrganizer, KAddressbook, etc. so it assumes you will use those as your desktop organizing apps and will print from there.
For a GUI that lets you install to the Palm I've used kpilot and jpilot. There are also plenty of command-line tools that allow you to do backups of the Palm (in fact lots of the GUIs are built on top of the same command-line tools).
My biggest gripe is that none of the tools I've tried is really good at printing. Jpilot is OK but has a few bugs and kpilot doesn't print at all.
Also, some add-on software has corresponding desktop software that is Windoze only but you can generally use it on the Palm only.
As a Dr. have you ever used epocrates for the Palm. It's a pretty cool app for drug referencing (at least it seems cool to me, a non Dr.)
Certain types of research have bias built-in. If BigDrugCo wants research results on NewExpensiveDrug they aren't going to farm the research to the people who told them their last drugs were worthless. Therefore, if I want BigDrugCo's $$$ in the future I'll try to design the study and present the results in the most positive way. Whether or not I'm aware of it there will be some underlying pressure.
As such, I feel that this type of study needs what I've coined a "triple-blind study" in which a neutral party is placed between the funder and the researcher.
This neutral party would then choose researcher(s) at random from a pool of candidates qualified to do the research and frame the question in a neutral way. The funding source and desired outcome would be withheld from the researcher.
It's a word in the English language. You see, there is this thing called a "dictionary" that allows you to answer this sort of question.
Now technically they probably meant guarantee since guaranty and guarantee are slightly different. Although guaranty can be used for guarantee it more often is used where the agreement is an assurance of financial payment.
As a side note, I used to work for a bond insurance company which, due to mergers, doesn't exist anymore. The company name was "Capital Guaranty" and we were in the Steuart tower of a building in San Francisco. If I didn't spell out everything I would end up getting things sent to one of the many combinations of Capital/Capitol Guaranty/Guarantee in the Steuart/Stuart/Stewart tower...
Worse still was growing up at the (then named) Naval Weapons Center, China Lake. When you get something sent to the Navel Weapons Center it conjures up all sorts of scary images.
I still have my Poqet PC from ~1989. Fujitsu bought them out and while they haven't been made for years, you can still find them on eBay - usually for less than $100.
80x25 screen, MS-DOS, keyboard you can touch-type on, Lotus 1-2-3, etc. It's instant-on and runs for weeks on a pair of AA batteries. It won a 1989 Byte award of distinction.
I suppose a Palm with a folding keyboard might do the trick nowdays but the Poqet was (is) a slick little machine.
Last two times I've lost dialtone it's taken days to get it back up. They simply don't work on the problem after hours 'cause it costs them overtime. The days when the phone company rushes to fix a problem are long gone.
At least, unlike some projects, a Google search on "moodle" returns information relevant to the project. It used to be that a simple search for "postfix" returned pages on programming syntax. Now, possibly to the annoyance of those searching for syntax info, almost all the results are for the Postfix mail server.
Apparently geeks make more web pages or Google is biased toward geeks since a single word search on jakarta, ant, apache or forrest returns as the first hit the Apache foundation project page rather than info on Indonesia, insects, native-americans/aircraft, or woodlands.
Corporations spend big bucks on product naming. They need to know if it is copyrighted or trade-marked world-wide, whether it is potentially offensive in any region where they intend to market the product. They run market-research to find how consumers respond to the various names. Most open-source programmers are more interested in the quality of their creation than in spending time or funds on product naming research.
From the Moodle site:
The word Moodle was originally an acronym for Modular Object-Oriented Dynamic Learning environment, which is mostly useful to programmers and education theorists. It's also a verb that describes the process of lazily meandering through something, doing things as it occurs to you to do them, an enjoyable tinkering that often leads to insight and creativity. As such it applies both to the way Moodle was developed, and to the way a student or teacher might approach studying or teaching an online course. Anyone who uses Moodle is a Moodler.
I don't know the full capabilities of Blackboard but I would look into moodle as an alternative.
Admittedly, I don't tend to read volumes of cost comparisons between open-source and proprietary software but one thing I haven't seen in the cost comparisons I have read is the cost of managing licenses. In my experience this is non-trivial.
As you have noted here there is a cost in wasted time dealing with the vendor and probably in down-time for your users who need the software.
Even if the key wasn't lost there is a cost in maintaining the records of keys.
If you can't convince them to provide you with your key then there may be the cost of buying another copy if you decide to continue doing business with the crooks who are currently screwing you.
I have personally spent days with tech-support trying to work around buggy activation schemes. This was not only lost time for me but for the projects that relied on the equipment in question.
I've also had to battle with vendors to get rid of evergreen clauses or to carefully track them when they couldn't be removed.
Then there is the recent issue with certain Adobe software not installing on machines with RAID arrays (you are installing on multiple disks which is prohibited...). Go figure.
And the issue of Intuit not providing keys for old versions of software even though they acknowledge that they have them. Upgrade or kiss your data goodby.
When you add users or machines you need to track your license status, get purchase orders, etc. Renegotiating bulk contracts, watching out for evergreen clauses and such takes legal and management time.
One need only scroll through a few of Ed Foster's "Gripe Line" columns from InfoWorld to see how much pain product activation is causing.
Good luck.
It's a simple web-based logging system (single stand-alone executable availabile for *nix or windoze) that you can get running in just a few minutes. We use it for tracking issues with vendors, entering changes to machines, etc.
It's free and the opportunity cost is only an hour or so. It won't do everything but it will probably meet your needs and you can impress your coworkers by having it up and running by the end of the day.
Why wouldn't they? Oil doesn't conduct. That's why it's used for cooling in electrical devices such as transformers, dummy-loads and such. I recall one vendor who demonstrated the high breakdown voltage of their oil by running a TV set in a vat of the stuff. Almost anything has better heat removal ability than air and for silent running it's not a bad idea.
There is still the problem of removing the heat. If there is enough surface area to allow the heat to be removed then you are ok, otherwise the oil (and everything else) will get too hot. Encasing everything in a metal box with fins on the outside would probably keep things even cooler.
last weekend (a friend works for ILM). It is most definitely the best of the recent three. The progression toward the creation of the Empire and the conversion of Anikin to Darth is nicely done and the creation of the Empire bears a scary resemblance to current US politics.
One scene (you'll know it when you see it) was distractingly similar to the Black Night scene in "Holy Grail" and given that this one ends roughly 20 years before Episode IV one can quibble about the age of a couple of the characters. Manikin Skywalker is as wooden as ever but all in all it was a fun time.
The biggest problem was that the early morning line snaked way too close to Starbucks leading many of us to drink way too much of the dark stuff right before a 2.5 hour movie. And when you see movies with the movie-makers _nobody_ leaves before the last credit scrolls off the screen.
But often you can rename them even when you can't delete them. It's always worth a try. On reboot it can't find the offending file.
Read the rules. They clearly state "Contest open to anyone at least 18 years old as of date of entry. Void where prohibited by law." Guess they won't need to buy that Xbox...