If you know the password, your (human) perception would be that it takes slightly longer to open. The actual processing time required though would be significantly greater.

If you don't know the password, it takes that extra processing time *for each password you try* i.e. it's multiplicative. So if you're trying 300 passwords, for the part which takes 300x as long per password, it's now 90000x as long (for that part) to go through the full list.

http://www.pccasegear.com/inde...

I used to buy from AusPC Market a long time ago. These days I normally use PC Case Gear.

Our current government are arseholes. Yes, I am saying the other mob is better. Not much better perhaps, but better than this bunch of complete dicks.

Don't get me started on what they've done to our National Broadband Network.

No, I didn't vote for them.

So exactly what do you get with Groovy that you don't get with Jython (Python on the Java VM)? Apart from different syntax of course ...

One of the great things about Python is it runs just about anywhere. There are even embedded versions.

The only real problem with Jython is it doesn't implement Python 3 yet.

And of course, typo. "... pretty much".

https://github.com/OpenELEC/Op...

Just determined in the last week to be due to async suspend/resume. From the various reports, oretty much all Intel hardware is affected.

I work from home ~95% of the time. I try to stick to a 40-hour week, but quite often I push into 45 or 50 hours.

The thing is, I don't have a commute. I start working almost immediately after waking up; eat breakfast while going through emails from the US; take a few breaks during the day (including for lunch), and usually finish around 3pm.

But if I'm heavily involved in something (I'm a software developer), I might keep working until 5pm, or even dinner. If I do that a couple of times in the week, I've hit 45+ hours.

I had a commute, that would be 40 hours a week *plus* 5-10 hours depending on traffic. Plus as a contractor I'm billing for all the hours I work ...

"here in Australia" - not British ;)

Unfortunately, the voting system in the US (plurality) is heavily biased towards a two-party system (whatever the intentions of the founding fathers). It's better here with an instant-runoff system, but still not ideal (there are still strategies where voting for your preferred candidate is not the best option, but they're much much rarer, and almost impossible to predict where it would be effective).

What does happen in Australian elections (where voting is compulsory - approximately 98% of eligible voters voted) is that a small number of swing voters can have a disproportionately large effect in our lower house. The current government won in a landslide in terms of numbers of representatives (90 to 55), but only had 53.5% of the two-party preferred votes (there are also a couple of independents).

If you mean bipartisan by "center [sic] ground" then I'd agree.

However, I don't think it's left vs right so much as centre-right (Democrats) vs right-extreme right (Republicans). Very few are actually on the left anymore in the US (and it's going that way here in Australia as well unfortunately).

There might even be less bipartisanship here - our current government got in on an "Anything Labor did was bad, we have no policies of our own" platform ... and damn are they delivering on their lack of policies.

I wonder if such stoves would meet the standards if SmartBurn was used:

http://www.smartburn.com.au/

Their pitch sounds like the usual snake oil, but the things really do work. My parents have been using them for a few years now and the change is incredible (and was noticeable within a few days).

All the baked-on sap, etc on the inside of the glass went away, there is noticeably less obvious smoke (smaller particulates) and more complete combustion inside the fire, and my parents haven't had to empty their chimney since they started using it.

I have no idea what is in the things (it's a Trade Secret) and no association with the product other than having seen them in action.

It is *not* illegal to enter Australia via any means to seek asylum, despite what so many of our politicians say. There are zero "illegal asylum seekers".

Asylum seekers may well perform illegal acts or use illegal services to get to Australia, but the actual act of coming to Australia to seek asylum is not illegal, whether they come by boat, plane or walk across the ocean floor.

They may be determined not to be asylum seekers, in which case their continued residence in Australia may be determined to be illegal, but that is separate from the act of coming to Australia to seek asylum.

Wish I could mod you up - OP read the parent of this post!

No - courts close loophole, loophole can't be used anymore.

Laws that take away freedoms (e.g. making something a crime) or property (e.g. taxes) must not be retroactive. This includes loopholes - if use of the loophole was determined to be legal under the law as it was at the time anything gained from it cannot be taken away.

I dislike people using loopholes to advance themselves as much as anyone, but not setting precedents of making retroactive legislation is more important.

I know that SSHDs work. They work pretty well for what they are. But they don't work as well as an HDD + SSD cache drive when that is an option (which it isn't always).

And guess what - it's possible to have a check box "Add SSD cache drive (faster performance)" as well. As much as a year ago I started seeing Ultrabooks configured with HDD + mSATA SSD cache drive out of the box (in fact, my current work machine is one of them - although I replaced both SSD and HDD ...). The initial boot image configures the system to use it and the user generally won't even be aware it's been done that way (unless they're a techie and investigate).

This week I was speccing out a system for a family member (not a techie). I showed them the options of HDD, SSHD (this very Seagate that is being discussed) and HDD + SSD. They were told that with the normal SSD install (OS on the SSD) that file management would be trickier, but I don't think it registered. They "knew" that SSDs were fastest and so wanted the SSD.

I will be configuring it to use the SSD as a cache + fast storage. Some games will be installed initially to the SSD. When using it they'll probably never even think about the fact that there's more than one drive in there - they'll just install as per normal and leave the cache drive to deal with it.

BTW, configuration of an SSD cache drive is (on Windows):

1. Set SATA ports to RAID (this is unfortunately vital).

2. Install OS to HDD.

3. Install Intel Smart Response Technology software/driver.

4. Open SRT and enable caching.

In general, I don't see a lot of use of an SSHD on the desktop, at least not with only 8GB of NAND. There are significant advantages for a system (such as a notebook) where there is only a single available storage option.

However, if you have the capability to have both an SSD and an HDD you have a couple of much better options (e.g. on a notebook with an mSATA port or any desktop).

1. Install OS to SSD, manually manage installing things to HDD.

This will generally give you the fastest performance for the things that really need them, but you're losing a lot of your SSD to OS + hibernation file (if enabled) and you have to know how to manage multiple drives effectively.

2. Install OS to HDD, dedicate a portion of the SSD to caching (e.g. with Intel Smart Response Technology) and use the rest for things you always want SSD performance with.

This gives very simple drive management - by default you install everything to the HDD. The SSD caches the most-used stuff and you can manually move things which benefit most from SSD characteristics to the SSD. Definitely the easiest setup to usefully use an SSD when setting up a machine for someone else.

BTW this is how I've got my ultrabook set up (32GB SSD cache, 80GB SSD data partition). The 32GB of cache is approximately equal to the Windows 7 OS + Hibernate file (16GB RAM) so I'm not really losing any space, but it's being used more usefully. And things which greatly benefit from fast random access (e.g. source code trees) are on my SSD.