Update: I just opened one of the Truecrypt-compatible containers I had
created (but wouldn't=20
mount) that was 2.0 gigabytes in size using TrueCrypt (for Windows).
However, it told me=20
that the container was unformatted, and offered to format it for me.
So it seems that within-container file formats are indeed the problem.
Whatever Scramdisk=20
is using to format (or to read formats) of anything else other than
FAT12 isn't working,=20
Stewart
> ______________________________________________=20
> From: Millen, Stewart =20
> Sent: Wednesday, August 22, 2007 5:50 PM
> To: 'sd4...@li...'
> Subject: New (Linux) User Problems with Scramdisk for Linux 1.0-2
>=20
> I'm a long-time Windows user of Scramdisk and have now purchased a
> Linux box (Dell) with
> Ubuntu Feisty 7.04, determined to make the switch to Linux.
>=20
> I downloaded the deb file for Ubuntu 7.04, and also (when told it
> needed the Trolltech libqt3-mt
> dependency) the libqt3-mt library from the Ubuntu software universe:
>=20
> http://packages.ubuntu.com/feisty/libs/libqt3-mt
>=20
> After I did this, SD4L installed and opened apparently succesfully.
> But what I'm seeing is:
>=20
> a) I can create and open small (like floppy size, 1.4 megabyte)
> containers created by either
> SD4L or legacy Windows Scramdisk OK.
>=20
> b) I can open small (1 megabyte) containers created with TrueCrypt (on
> a Windows machine)=20
> OK, irregardless of the algorithms chosen.
>=20
> c) Containers larger than floppy sized (I've tried down to 500
> megabytes) cause the=20
> OS to lock up completely requiring a hard reboot after entering the
> password and trying
> to mount. This is irregardless of the hash algorithm, encryption
> algorithm, or file format=20
> chosen. It is also irregardless of whether the containers were created
> with SD4L or=20
> whether they were created by TrueCrypt on a Windows machine.
>=20
> d) When walking away from a container creation for "large" containers,
> sometimes I come
> back to the desktop seeing that SD4L has closed in the process of
> container generation.=20
> When attempting to create containers bigger than 2 gigabytes, I always
> get containers of=20
> 2.0 gigabytes irregardless of the size chosen. Needless to say, all
> these freeze up the OS=20
> when I try to mount them as per above.
>=20
> I see on the Ubuntu forums that one other user has complained about
> not being able to=20
> mount containers, and I also see here there is a problem with
> containers larger than 2=20
> gigabytes. However, apparently some users are succesfully creating and
> using containers
> up to 2 gigabytes, which I can not.
>=20
> So...(and remember I'm a complete Linux newbie)...is there some other
> library or dependency
> that I've not fulfilled? Do I need to install something else? What am
> I doing wrong?
>=20
>=20
|
