Can't use wired inet.

[labeas]

TC<x64> works nicely from a USBstik.

Also [importantly] with some of my good-old 32bit apps.
I've never found an adequate explanation why some-only 32-bit-apps
run under Win:x64 ?!

TC's X Terminal default font is a bit too small, but the VT font,
especially colored-on-black is perfect.

Since I can't see how to edit /etc/inittab [on the USB file which
starts TC] I'm able to get N extra ROOT VT's by N times `sudo openvt`

The VT(s) can run ETHOberon [for linux] in FrameBuffer mode - nicely.
But my other 32bit killer apps. <*nix Oberon> and wily [based on ETHO]
don't run - yet.

I need to be able to see & CutnPaste multiple TextFiles on the same
screen; but simple old `dmtm` 32bit, doesn't run.

For me `mc` is essental [especially if I have no wily].

Installing `mc` via a M$Win laptop with only WiFi access is not
intended for TinyCore.      Should I try:
* find the URL of TC's <mc file>;
* use Win to d/l it;
* move it to TC's USBstik;
* ...... to install to USBstik;

As is evident, I can't comply with TC's intentions of:
  "just fetch the binary from the cloud, when you need it".

Thanks for any advice.

==labeas

[Juanito]

You need to get wired or wireless networking to work on your usb stick install.

If you have wired networking and your router provides dhcp, things should work if you plug the cable in.

If you have wireless networking, you will first need to find out what hardware you have using either the pci-utils or usbutils extensions.

[labeas]

> You need to get wired or wireless networking to work on your
> usb stick install.

No. If I wanted to follow the herd, I'd use M$Win, or better still
tomorrows <Tablet>.

> If you have wired networking and your router provides dhcp, things
>  should work if you plug the cable in.

That condition is not expected.

> If you have wireless networking, you will first need to find out
> what hardware you have using either the pci-utils or
> usbutils extensions.

That's for later, after it's confirmed that I can increase the
X-font size. HCI considerations trump <technology>.

I've got a 3G-dongle plus subscription which is auto-driven by M$Win.
Previous 3G-dongles, I was able to drive from my old pppd scripts,
 by first:
* detect USB device plugged and seen as a CDROM;
* eject USB-CDROM: causes it to switch to modem mode;
* symbolic-link from /dev/modem to <USB device>;
* talk pppd as per 1990s.

What about increase X-font-size and install mc via M$ fetch the
 the TC:mc-package; as asked in my OP? Usability trumps technology!

Thanks,
== labeas

[Juanito]

'not sure you'd buy a 3g dongle that only supports windows 

In general to download a corepure64 extension you need:

http://tinycorelinux.net/7.x/x86_64/tcz/extension_name.tcz
http://tinycorelinux.net/7.x/x86_64/tcz/extension_name.tcz.dep [not always present]
http://tinycorelinux.net/7.x/x86_64/tcz/extension_name.tcz.md5.txt

When the *dep file is present, you will need to repeat the above for each extension named in the *dep file recursively.

[curaga]

Perhaps you can download things in a VM? Virtualbox, etc, are free.

By running TC in the VM, using Windows' internet, you can download extensions easily to the virtual disk, then move them to your usb install.

[patrikg]

Have seen somebody take out the 3g dongle firmware from the $MS environment and used with linux.
You can search, for that to maybe add the support for the 3g dongle to linux like tcl.

 

[labeas]

I'm waiting for a reply to my yesterday's post that:
YES the installation of the 3 <extentions> started the WiFi.

Bottom-bar Icon appears & dmesg confirms.
But ping/s fail.
I can't find any commands to proceed to the next stage.
Please advise.

[patrikg]

Please don't post this begging/bumping messages.

[labeas]

WiFi works nicely on TC64.
I'll post a log later.
Thanks for TC.

[coreplayer2]

We're so glad you got the reps sorted out
Good job


Sent from my iPhone using Tapatalk