I see no one has done a fresh installation of Tiny Core on a pristine XP system
Wellll... this system lost its "pristine" virginity long before TC came along.
You're right and I apologize for being somewhat selfish there.
This is a WinXP Pro 32 bit system with 1 physical HD with several partitions. For now, we'll pretend there's only one and that's sda1, formatted ntfs.
From the rc2 changelog (above):
Typical instructions for tc-grub4dos.gz via Windows from a base no network Tiny Core boot.
1. Use Windows to access and download tc-grub4dos.gz typically this is save to:
Documents and Settings/user/Desktop
2. Boot from Tiny Core CD or unetbootin pendrive. This results in a base norestore (cloud) mode.
3. Use mount tool to mount your Windows drive.
4. Use Control Panel -> Load Starter Pack to navigate Windows drive to load tc-grub4dos.gz
5. Use Run icon and type tc-grub4dos. Program begins...
1) Ok, I was really using tc, but the effect of the file download is essentially the same. Got the file, tc-grub4dos.gz.
2) I already had bzImage and tinycore.gz on sda1 in boot/tc3.7rc2 ( I actually already had them booting by invoking grldr from boot.ini - sort of the opposite of what I ended up with below ). Booted with "base" and "norestore" to simulate booting from CD.
3) Used mnttool to mount sda1
4) Used Control Panel -> Load Starter Pack to navigate Windows drive to load tc-grub4dos.gz
5) Used the "Run" tool to run tc-grub4dos
Step 5 didn't work the first time I tried it, but it did the second time so I suppose I had just fat-fingered it... or maybe related to the issue Guy mentioned above?
Worked through the GUI installer - no problems. There's room for improvement in the prompts/labels - a little more reassurance for the underconfident, maybe - but overall it just worked.
Since I had already fiddled around w/grub4dos manually and installed it to be called from the Windows boot loader, I expected this process to give me a third entry in boot.ini. I was only a little surprised to see grub come up -before- the Windows boot loader. Of course the Windows boot loader is still able to invoke my original grub menu, which makes for a very -unusual- sequence of menu screens!
While I've done some serious geekery on the test system in the recent past, I'm relatively confident that none of that affected the validity of the results of the current test.
At the end of the whole process, the bottom line is "the install process with grub4dos.gz just plain works and you couldn't ask for it to be a whole lot easier". Another well deserved "Thank you", roberts.
In contrast, my manual efforts worked, but not 100% correctly, and were only easy for me because I'm a geek and have been fooling with TC for a long time.
I'll be away from computers until after the weekend but at the next opportunity I will try the installation on an XP system that, while again "not pristine" has had any OS but XP on it.