Hello,
I'm going to install eComStation 2.0 RC7 in my Eee PC 904HD and I want to know if I need to partition or format my HD, because the notebook have a 80GB HD and as I know FAT16 partitions only can hold 2GB, but I can install it in another type of partition, like NTFS, FAT32...
Another thing that I want to know is, the installer of eComStation 2.0 RC7 can automatically partition my HD?
Thanks,
Nathan Paulino Campos
You can install eCS in a HPFS or JFS partition. HPFS supports partition sizes up to 64 GB. The eCS installer comes with a partitioning tool called MiniLVM that is invoked when you press "Create volume" in the respective installer page. Not automatic but rather easy to use.
Thanks very much chennecke! ;)
Use JFS. Better performance than HPFS (IMO) and quicker drive-checking if you ever have a crash/freeze.
Only one problem - there is no way to recover anything on a JFS partition if anything really goes wrong.
Doesn't JUNE work acceptably?
http://en.ecomstation.ru/projects/jrescuer/?action=desc
Thanks, i will take a look! :)
If I recall correctly, you have to run the Yoda script (included in the Downloads) in order to write filenames so that June can recover the files with names, instead of just random letters.
Hi,
Saijin is right there... and if you look in the rexx scripts section here you'll find a version or two that does it as well. You may want to scedule it to run once in a while on each drive.
Quote from: Saijin_Naib on 2009.09.30, 03:23:32
If I recall correctly, you have to run the Yoda script (included in the Downloads) in order to write filenames so that June can recover the files with names, instead of just random letters.
You can recover the files with dfsee as well, and it may be somewhat more stable, but I'm not sure if it support the Extended Attribute approach as June does.
//Jan-Erik
I recommend creating 2 partitions for your eCS.
(1) The "system" one, which will contain only operating system related data and apps. You will install eCS here. Later on, you will put anything here only if it is a "system-wide thing". This partition can be relatively small. 2 GB is more than enough. Make this partition HPFS - it's too small for JFS giving you any considerable benefits and moreover, HPFS is a long time used (therefore, long time tested :) ) file system written by IBM.
(2) The "data" one, which will contain everything else. You will keep your data and apps here. Note that eCS is not winblows so that if you command "install on D:\mydir", the app will install on D:\mydir and not on C:\winblows. Give the partition the rest of your disk (or the rest of space reserved to eCS). Make this partition JFS - HPFS is painfully inefficient on large partitions and moreover, it has the 64 GB limitation.
Therefore:
(a) During install, select "Custom" installation.
(b) Create 2GB partition - this will be your system. Make it "installable" and "startable" because you will install here.
(c) Create the data partition. Save changes and quit FDISK.
(d) Format the 2 GB partition as HPFS. You can even afford the luxury of having the partition checked on errors. It's small so that it will not take a long time.
(e) Install.
(f) Format the data partition from your installed system as JFS.
Hi,
this is perhaps off-topic for Nathan, but anyway...
Quote from: Radek on 2009.09.30, 10:19:05
You will keep your data and apps here. Note that eCS is not winblows so that if you command "install on D:\mydir", the app will install on D:\mydir and not on C:\winblows.
Ha! Wrong, my arse! The installer gives a SHIT about this.
Ever since I can recall eCS installs, that darn thing is unable to install the bundled applications correctly.
For years, all my programs were installed in C:\Apps. And every time when I installed an eCS, I told it in the installer to use "c:\apps" instead of "c:\programs". And guess what happens...
Yeah, you are right: That braindead little asshole of installer keeps pumping crap into "c:\programs."
My workaround?
I simply moved the crap over to c:\apps accordingly and ran a self-created script for changing INI entries and stuff to point to the correct location. At some point however I simply surrendered. Now I'm "happy" working with a c:\programs folder.
Yet another nail in the coffin of user acceptance in my mind.
Still, I sincerely hope that some bright sunshiny day someone will learn that installer to actually do things right. Perhaps RC -whaddeverversion- has corrected this in the meanwhile, but frankly, I am too tired to give it yet another and yet another try over and over and over again.
Cheers,
Thomas
Thomas, I read a few years ago some ones dissertation on how and where eCS should place files. At the time I wondered about the slavish following of windows by putting everything in one massive C: partition, where if anything goes wrong you're up s**t creak without a paddle.
Like Radek I use a small system partition (started years ago with 100 MB but now up to 1 GB) and all apps on another partition and data on yet another partition. It makes for easier backups and is simple to restore if anything goes wrong.
If what you say about the eCS installer is correct, and I see no reason to doubt you, then the person that wrote it has some explaining to do or needs to be de-brainwashed from their windows thinking.
Hi ivan,
for me the problem is not that someone decided to call the default "\programs" (at least it isn't "\program files" :) ) but rather the fact that some subcomponents of the installer simply seem to ignore the users choice and go with "the default".
If they would hardcodedly install everything into C:\PROGRAMS I can live with that. But if they offer a function to override it, that crap should work. Point. Otherwise it's just more of a nuisance than a benefit to have "parts" of the programs installed to your preferred directory.
And, hey - I didn't even check what would happen if you upgrade an existing installation instead of installing from scratch... wow, I wonder what might happen then...
Cheers,
Thomas
Upgrades DO NOT work on the RCs. I've tried it from 1.2mr to a 1.2mr and it just... was miserable.
I work off a similar approach. I keep one volume for eCS and my programs (8gb WD drive). I have all my data on my NTFS drive. Any data I need from eCS goes on a flashdrive or gets FTPd over to my xbox. I sometimes keep a small partition on the end of the drive which contains all the drivers, installers, etc so that when I do a clean install I just have to run all the installers and I'll be back up to how I was before the clean install.
I need a NAS device so I can get all data on that to share between Windows, eCS, Xbox, Haiku.
Thomas is right, it happens, but when it happens:
(1) Certain old IBM "suites".
(2) Most of apps ported from winblows, which use "Innotek runtime". They are still winblows apps, the runtime pretends to them that they are still running under winblows. And they still behave like winblows apps. They install to "c:\Program Files" - e-h-h - I wanted to say, to c:\programs, and they use "registration database" for storing their configurations.
(3) Certain Unix ports.
(4) Badly written packages with badly written installation scripts.
(5) Badly written apps with hardcoded "c:\programs" and similar places.
Well, we cannot avoid apps (1) - (5) completely :-\
Well written apps allow you to install them where you need them. There are only few "standard places" in OS/2 - root, \os2, \boot and some others. These dirs contain system data and the system will search its data there and (often) nowhere else.
Radek,
as always you gave it a perfect and unbiased summary. I like your style.
I wish I could keep myself so much matter-of-fact too... but sometimes, you know, my evil alter ego just wants to scream out loud "whaddacrap" when I see what other people are doing (while I would get my ass kicked for, if doing this at work). ;)
Cheers,
Thomas
Quote from: Saijin_Naib on 2009.09.30, 19:41:11
I need a NAS device so I can get all data on that to share between Windows, eCS, Xbox, Haiku.
Simply solved with a simple low end Linux or eCS box and some drives.