If you run it through VNC, VNC will give you a virtual memory-based
GUI that can be smaller than the display, with scrollbars.
Other tools that might do that too...
xnest - Nested X server
xserver-xephyr - nested X server
I'd use VNC myself, since I have experience with it.
On Fri, Aug 1, 2008 a
I think just adding my files to the file structure before the USB image
is created might work. I can also put in a 2GB file that I can later
delete on the target to create more spare space. I need to allow space
for the codecs and drivers along with the helix framework and players.
Jim A
On Fri,
On Fri, 2008-08-01 at 14:18 -0700, Rusty Lynch wrote:
> On Fri, 2008-08-01 at 17:07 -0400, Jim Abernathy wrote:
> > I want to build a bootable USB Flash R/W image on an 8GB Flash key.
> >
> > I have done this with image-creator and run on a small 1G flash key. Now
> > I want to build a 8GB flash b
On Fri, 2008-08-01 at 17:07 -0400, Jim Abernathy wrote:
> I want to build a bootable USB Flash R/W image on an 8GB Flash key.
>
> I have done this with image-creator and run on a small 1G flash key. Now
> I want to build a 8GB flash bootable R/W image so I can add .mp4 videos
> for a demo. When I
Jim,
If I understand your question correctly, you successfully wrote the
usb image on to a 8GB flash drive. And then you tried to copy media
files to that flash drive and there wasn't enough space.
MIC uses dd to copy the image file over to the usb flash drive. So the
usb flash drive will be
I want to build a bootable USB Flash R/W image on an 8GB Flash key.
I have done this with image-creator and run on a small 1G flash key. Now
I want to build a 8GB flash bootable R/W image so I can add .mp4 videos
for a demo. When I followed the same process as before, it worked, but I
seem to have
I would love to be able to use Rosetta Stone on my Samsung Q1 Ultra. I
installed with wine and it installs and runs fine. Except things do not fit on
the screen and I can't ever quit the program, or click on several of the menus.
I assume there is either a way to scroll up/down/left/right or con
I went back and did 'aptitude purge moblin-image-creator' then
reinstalled the package. Now image-creator works, but this time when I
loaded the same tarball, I names it menlow-lpia-ume. I got a similar
error:
[EMAIL PROTECTED]:~$ sudo image-creator
In on_Load_activate
Project name: menlow-lpia-um
Hi Jim,
You are getting this error because you have added an unrecognized
project. The platform 'menlow-lpia-ume' is probably not defined in your
platform definition.
You can get rid of this problem by removing the .proj file
in /var/lib/moblin-image-creator/projects dir (or
/usr/share/pdk/
I downloaded the Moblin Image Creator project tarball:
mid-8.04.1-menlow.mic.tar.bz2
When I tried to load the project, it ran for a while then a key error
occurred. Now every time I start sudo image-creator, I get the following
error:
Traceback (most recent call last):
File "/usr/bin/image-creat
McCaslin is the name of the platform that came before any of the Atom
based platforms (like Menlow.) McCaslin has a Celeron ULV.
As to the original question... I have never tried the prebuilt UME image
for McCaslin, but I build my own images with no problem using moblin
image creator.
--rusy
Thnx for the information Emmet.
I will install Pbuilder and try to compile the kernel. But for now I will
read your comment and the wiki closely, because it is a lot of new
information ;)
Greetz
Bob
On Fri, Aug 1, 2008 at 4:18 PM, Emmet Hikory <[EMAIL PROTECTED]> wrote:
> Bob Peters wrote:
> >
Bob Peters wrote:
> My workstation is 64 Bits and my target is 32 bits both x86 when I tried
> this command to build the kernel, when I was chrooted in the Menlow image:
>
> dpkg-buildpackage -b
>
> I got an error, something about the 32 and 64 bits incompatibility. Now my
> question is how can I
Victor Palacio wrote:
> It's supposed to work...
>
> I mean, a bootloader, kernel and filesystem created for McCaslin
> platform will work on an old Q1.
>
> I though McCaslin was based on Atom CPU, and old Q1 is based on Celeron ULV.
>
> Regards,
The Mccaslin build is for the Q1 specifically.
Hi,
Yesterday when I want to compile the linux kernel from the moblin project I
ran into a problem.
My workstation is 64 Bits and my target is 32 bits both x86 when I tried
this command to build the kernel, when I was chrooted in the Menlow image:
dpkg-buildpackage -b
I got an error, something
It's supposed to work...
I mean, a bootloader, kernel and filesystem created for McCaslin platform
will work on an old Q1.
I though McCaslin was based on Atom CPU, and old Q1 is based on Celeron ULV.
Regards,
On Mon, Jul 28, 2008 at 11:34 PM, Chris Gregan
<[EMAIL PROTECTED]>wrote:
> Victor Pal
16 matches
Mail list logo
