malc.

Whilst transferring 5 files at a time from my laptop to my pc via a usb stick, guess what?

My hard disk ran out of room. ROFLOL

Anyway the good news is…
1) I found a screwdriver
2) I found the external hard disk power supply

So windows is slowly formatting said drive.
When it is done, I can dump the video files off on to the new external and free up my desktop drive to.

Moral is I guess you can’t cut corners, even if they seem like they will take a ridiculously long time that it isn’t worth it, when a shortcut (no matter how illogical and bizarre) seems to be an alternative.

I still have no idea why my dvd drive won’t read the video library disks. I guess we solve that with a new $30 drive.

And yes, I certainly should stop Windows 7 being helpful and sort out the networking manually.

Either way you look at it, 30 hours later and I still haven’t found the video element I want.
But the business marketing management software has come a LONG way

Strange how things turn out ?!

It really seems like cashing in on a pandemic.
They GLOAT about realistic images of a real N1H1 virus.

Hmm. WDYT?

So that’s how the cucumbers do it.

They pretend and get my sympathy, when all along – LOL

Anyway the concept remains useful I think, so I’ll leave the post as is.

From the huge list of discussions, searching for case P034520 seems to bring you to
http://www.ftc.gov/os/comments/endorsementguides2/index.shtm

But I see no feedback form, only posts from other “officials”.

If you find out where to respond to the FTC, please LMK.

After an inordinate amount of discussions, both in public and privately, on the situation regarding codecs for

I have therefore removed the two subsections in the HTML 5 spec in which codecs would have been required, and have instead left the matter undefined, as has in the past been done with other features like and image formats, and plugin APIs, or Web fonts and font formats.

The current situation is as follows:

* Apple refuses to implement Ogg Theora in Quicktime by default (as used by Safari), citing lack of hardware support and an uncertain patent landscape.

* Google has implemented H.264 and Ogg Theora in Chrome, but cannot provide the H.264 codec license to third-party distributors of Chromium, and have indicated a belief that Ogg Theora’s quality-per-bit is not yet suitable for the volume handled by YouTube.

* Opera refuses to implement H.264, citing the obscene cost of the relevant patent licenses.

* Mozilla refuses to implement H.264, as they would not be able to obtain a license that covers their downstream distributors.

* Microsoft has not commented on their intent to support

(Sorry if I’ve mischaracterised any positions above; the positions are relatively subtle and so it’s likely that I have oversimplified matters.)

I considered requiring Ogg Theora support in the spec, since we do have three implementations that are willing to implement it, but it wouldn’t help get us true interoperability, since the people who are willing to implement it are willing to do so regardless of the spec, and the people who aren’t are not going to be swayed by what the spec says.

Where did all the other posts go? I was linking to your blog to show an example of all the problems with Wellman’s AutoPilotFX product but all the content has gone.

Thanks,

Ben

http://www.headzoo.com/alinks

Of course he has now fixed the anomaly.