Jim's Depository

Very strange indeed. I still don't understand why every Lua implementation (except for luasp.org) seems to be done backwards. Why doesn't anyone try to take the php approach and allow web designers to work on designing instead of doing strange script-fu just to use Lua?

unfortunately JPEGInfo will not catch all.

the tool above catches the rest

I found a much simpler solution, there is a tool 'Corrupt JPEG Checker' for Mac OSX.

It can be found here: http://www.failedinsider.com/corruptjpegcheckermacosx/ or in the mac app store.

Saved me a lot of time.

http://www.failedinsider.com/corruptjpegcheckermacosx/

Jim,

I realise you did this 2 years ago now, but this is really awesome. I'm a bit surprised there's not more attention drawn to:

adding transparency to the JPEG specification in a standards-based way and
your stop-gap solution.

This may certainly come in handy for some client one day, thank you for exploring this and developing tools for us to use even!

Just curious though, why are you using uncompressed PNGs for the alpha channel? It would seem to me that embedding a grey-scale JPEG layer into the original JPEG would yield a much more compact solution and the benefits and pitfalls of lossfully compressing the alpha-channel should be very understood by the wielder of this solution.

Given the apparent intelligence reflected in your posts, it is obvious to me that you had already considered this, but yet you went with embedding a PNG into a JPEG. Do you have a post somewhere that details your logic here? If you're not interested in blogging about it, please drop a note at 'm' followed by 'j' followed by 'k' at sisuconsulting.com. Many, many thanks in advance!

Hi! I am trying to do something similar with the photo frame, but I am not being able to install a new firmware on it. Any ideas? How did your project go?

Anyone has the email address of the guy (Hajo Noerenberg) who actually hacked it?

I tried to wave a rubber chicken and just throw every plausibly connected module at it, but it's still a no-go.

I've seen some indirect talk about mdraid + LVM + EXT4 not being a bootable combo yet, but then again I've seen people boast about their mdraid + dmcrypt + LVM + EXT4 / BTRFS setups.

I guess I will just fall back to a good old fashioned EXT2 boot partition.

Here's my rubber chicken waving approach for the internet:

GRUB_PRELOAD_MODULES="search_fs_uuid raid raid5rec raid6rec mdraid lvm ext2 chain pci"

update-grub

grub-install --modules="search_fs_uuid raid raid5rec raid6rec mdraid lvm ext2 chain pci" /dev/sda

Debian Squeeze, VirtualBox 4.0 from backports.

Debian 6.0.4 installer .iso

6 virtual disk devices
-> one physical raid partition per device
-> one RAID6 md0

One physical volume group
logical volume /
logical volume /home

The system does not manage to boot even after going in into the rescue mode and making sure grub is both configured and installed with the lvm module preloading (/etc/default/grub -> update-grub -> grub-install).

It all trips up in grub-pc (GRUB2) somehow and I do not know how to debug it.

GRUB loading.
Welcome to GRUB!

error: file not found.
Entering rescue mode...
grub rescue>

Any pointers? Did I miss and mess up any of the rescue mode superhero stuff?

Do you have any updates on your project? I have a pulse frame, but would like to know how to setup my own server if the bankruptcy goes bad.

Hi. Just came round searcing for info on the Kodak pulse frame. Any news about your webcam project? thanks. S.

I haven't actually mounted the resulting image file yet, but the conversion seemed to run OK. If you want to check your output image file contents, for information on what is actually in there, you can use the "disktype" package
from sourceforge (disktype.sourceforge.net). That program is also included in your favorite package manager. It'll make it a bit easier to figure out where your
partitions are located. This is a sample output, using my newly converted image file. "disktype myimage.img"

Regular file, size 31.00 GiB (33286000640 bytes)
DOS/MBR partition map
Partition 1: 29.31 GiB (31473008640 bytes, 61470720 sectors from 2048, bootable)
Type 0x83 (Linux)
Ext3 file system
    UUID 09DE2E1E-2C2F-4378-A8E6-59C8723865C7 (DCE, v4)
    Volume size 29.31 GiB (31473008640 bytes, 7683840 blocks of 4 KiB)
Partition 2: 2.687 GiB (2884632576 bytes, 5634048 sectors from 61472768)
Type 0x82 (Linux swap / Solaris)
Linux swap, version 2, subversion 1, 4 KiB pages, little-endian
    Swap size 2.687 GiB (2884624384 bytes, 704254 pages of 4 KiB)

more comments