WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Recent Posts

Pages: 1 [2] 3 4 ... 10
11
dCore X86 / Re: usb pendrives don't appear anymore on the desktop
« Last post by Jason W on May 23, 2016, 02:25:17 PM »
In the past did dCore-trusty with this enlightenment package show a usb icon when the usb was already inserted on boot?

I am running this enlightenment on dCore-trusty now and see that it works with the insertion and removeal of usb. 
12
dCore X86 / Re: IceWM graphic issues in dCore-wily...
« Last post by Jason W on May 23, 2016, 02:23:54 PM »
System Tools, Progams, etc are outside of the *Core Icewm menu population.  I will look in to restart Icewm.
13
dCore X86 / Re: IceWM graphic issues in dCore-wily...
« Last post by nitram on May 23, 2016, 01:46:27 PM »
Thanks, retested update, graphics good. Stock icewm.sce went from 17 -> 32 MB but re-importing with Xorg dependency back down to 18 MB. With the space saving strategies that can be used (dependency, list file, sce.purge file tweaks) IMO keeping extensions so small that things don't work is not a preferred route. Don't know if this is possible, maybe all dCore WM should come with an Xorg dependency out of the box to keep them small or are people still using Xvesa? IceWM is actually a very full-featured WM - alt/tab switch, menu icons, built-in themes, multiple workspaces, dozens of configuration options, built-in panel, clock, 'start' menu, system monitors...not your fault it requires so many dependencies to run properly.

None of the other suggestions recommended ~4 posts up were applied, hence System Tools menu still broken, Restart IceWM button useless and Programs menu not populated. Let me know if you can apply these fixes and i will retest, othewise move on to next project. Thanks.
14
TCB Q&A Forum / Re: Display output only in the left top corner ?
« Last post by halma on May 23, 2016, 11:58:52 AM »
sorry my mistake, xen* is a wildcard, so here is the right boot parameters:

cat extlinux.conf
Code: [Select]
DEFAULT xen3
PROMPT 1
TIMEOUT 1

LABEL xen3
MENU LABEL xen3
KERNEL mboot.c32
#APPEND /tce/boot/xen-4.7-unstable.gz --- /tce/boot/vmlinuz64 waitusb=5:root=UUID="6a608b93-5055-4afb-8207-3827177498b9" tce=UUID="6a608b93-5055-4afb-8207-3827177498b9" nodhcp noutc showapps syslog tz=Europe/Berlin host=xenbox kmap=de --- /tce/boot/corepure64.gz
APPEND /tce/boot/xen-4.7.0-rc.gz --- /tce/boot/vmlinuz64_6.4.1_3.16.6_xen waitusb=5 root=UUID="6a608b93-5055-4afb-8207-3827177498b9" tce=UUID="6a608b93-5055-4afb-8207-3827177498b9" nodhcp noutc showapps syslog tz=Europe/Berlin host=xenbox kmap=de pause --- /tce/boot/corepure64_6.4.1_3.16.6_xen.gz
15
Corepure64 / Re: TinyCorePure64-7.1 - mcookie issue
« Last post by Juanito on May 23, 2016, 11:09:13 AM »
I don't think so - you would need to boot corepure64 from the flash driver specifying "tce=tce64"
16
TCB Q&A Forum / Re: Display output only in the left top corner ?
« Last post by Juanito on May 23, 2016, 11:07:35 AM »
What is xen*?
17
TCB Q&A Forum / Re: Display output only in the left top corner ?
« Last post by halma on May 23, 2016, 10:43:10 AM »
Hi Juanito,

i have an legacy bios and i just using the bootpromp after the boot is done, (console), no X-Server started after boot is done,

and this is how i boot:

cat extlinux.conf
DEFAULT xen3
PROMPT 1
TIMEOUT 1

Code: [Select]
LABEL xen3
MENU LABEL xen3
KERNEL mboot.c32
#APPEND /tce/boot/xen-4.7-unstable.gz --- /tce/boot/vmlinuz64 waitusb=5:root=$BLKID tce=$BLKID nodhcp noutc showapps syslog tz=Europe/Berlin host=xenbox kmap=de --- /tce/boot/corepure64.gz
APPEND /tce/boot/$(basename $BUILDDIR/fs_mount/tce/boot/xen*) --- /tce/boot/$(basename $BUILDDIR/fs_mount/tce/boot/vmlinu*) waitusb=5 root=$BLKID tce=$BLKID nodhcp noutc showapps syslog tz=Europe/Berlin host=xenbox kmap=de pause --- /tce/boot/$(basename $BUILDDIR/fs_mount/tce/boot/corepur*)
EOF

even i can use the comment bootline too, to boot up

Thanks
18
Corepure64 / Re: TinyCorePure64-7.1 - mcookie issue
« Last post by madmax on May 23, 2016, 10:03:13 AM »
Hello:

When booting from CD tinycore will look for tce folders on other media.
OK, now I get it.
It's by design.

But, why does it look for 'plain' tce folder instead of a tce64 forlder which is the one with the 64-bit extensions?

If you install corepure64 alongside core on the flash drive you need to specify a different tce folder (eg tce64) to avoid mixing 32-bit and 64-bit extensions.

Would the CD boot properly if I add the tce64 folder from the *.iso (with all it's contents) to the flash drive?

Thanks in advance.

MM
19
Corepure64 / Re: TinyCorePure64-7.1 - mcookie issue
« Last post by Juanito on May 23, 2016, 09:55:35 AM »
When booting from CD tinycore will look for tce folders on other media.

If you install corepure64 alongside core on the flash drive you need to specify a different tce folder (eg tce64) to avoid mixing 32-bit and 64-bit extensions.
20
Corepure64 / Re: TinyCorePure64-7.1 - mcookie issue
« Last post by madmax on May 23, 2016, 09:48:57 AM »
Hello:

Either remove the flash drive and boot from the CD or install corepure64 alongside core on the flash drive.

Make sure you use a different tce directory. EX: tce64

Thanks for the replies.

A question though, I don't understand why the *.iso version (if this 'is' the problem) would try to load something from 'outside' its own directory structure (which is on the CD).

eg: there's no tce64 in the flash drive's directory structure.

Would this same thing happen if there was a 32-bit TinyCore install on a hard drive (in need of repair, for example) instead of on a flash drive and I wanted to fix it booting the 64-bit *.iso?

Thanks in advance.

MM
Pages: 1 [2] 3 4 ... 10