General TC > Tiny Core Netbooks
TCL on a pendrive to run an Asus EeePC 1000HA?
Zendrael:
--- Quote ---What interested me about Tiny Core in contrast to Coreplus was, in particular, the x-windows interface and the simple, straight-forward way everything seems to be arranged in the windows. I'm tired of fancy GUIs. But perhaps the Tiny Core interface is an option in Coreplus?
--- End quote ---
Think this way:
MicroCore is only the base system and base tools without graphics.
TinyCore is MicroCore + graphical tools and (of course) graphical interface (Xvesa in this case).
CorePlus is TinyCore + extra drivers and tools to setup your environment easily.
All the "extra" components that builds TinyCore and CorePlus are just extensions added to the MicroCore packed in new iso images just to show how Core is extensible (and to help a lot of people!).
Mike7:
Hi, Rich.
--- Quote ---You want to be extremely careful with the dd command. If you get the of= parameter wrong, you can overwrite data you did not intend to.
--- End quote ---
Yes, it is worrying. I've been using of=\\.\e: Is that correct?
Rich:
Hi Mike7
--- Quote ---Yes, it is worrying. I've been using of=\\.\e: Is that correct?
--- End quote ---
I honestly don't know. The link that tinypoodle provided in Reply #14 looks to be pretty informative.
Mike7:
Hi, Tinypoodle.
Thank you very much for the chrysocome.net link. I can't recall where I downloaded my copy of dd.exe from, but it appears to be the same one since it was also dd-0.5.zip.
I am studying the info chrysocome.net gives on how to use dd. Apparently I made some mistakes. For example, I noticed that dd has once or twice filled up my entire 4Gb pendrive from an input iso of 100Mb. Maybe the --size operator can solve this (although it's unclear whether they are talking about the file being read from or the file or device being read to).
The filter addition for safety is a great idea. But are their dd programs being run as full executables? The one I downloaded will only run in the command line/terminal (I put it into C:\Windows\system32 so it can be run at any level). As a Windows terminal command, how can you add a <filter>? Or will <dd-removable> actually work in the commandline?
Another very thorny question is the naming of if= and of=. I've been using the name of the iso as the input file, and \\.\e: as the name of the output file. I wonder if this is correct? In the chrysocome.net documentation, there are two different Windows designations, although it seems to suggest that for XP (my op sys) the \\.\x: designation will work. Do you think that's right? I wouldn't like to risk using the \\?\Device\Harddisk1\xxxxxx designation for a usb drive. Too scary.
Here's what I've been putting on the terminal commandline:
>dd if=xxxxx.iso of=\\.\e:
It either never stops running, or else after a whiles it returns:
xxxxxxx bytes in
xxxxxxx bytes out
In that case, it seems to be working. The problem is that it's writing to the whole pendrive! (What it may be writing beyond the 100Mb I have no idea.)
I'm also rather worried that I may have made my pendrives inoperable now by using the dd command incorrectly in some way. Is that possible? Won't re-formatting them restore them? This is my most serious worry of all. It could explain why I can't get anything to boot on them, regardless of the installation method used. Very worrisome indeed.
I really would like to figure out how to use this command properly because I think it could be the solution to my problem. It certainly seems like the easiest way to make a bootable usb stick from a hybrid iso.
I hope you and others in the forum will help me out with this.
Cheers!
Mike
Mike7:
Thanks, Zendrael. That cleared it up.
Cheers!
Mike
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version