[ilko_t]

Quote

GUI mode started from second disk, but gives error NTLDR not found , since XP Bootfiles were made on first harddisk. Booting from first harddisk will let you continue with GUI mode, since boot.ini refers to Install partition.

Thanks, so it works as expected.

Quote

The BOOTWS folder when adjusted with the mapping strategy of cdob will do better and create always XP bootfiles at the Install partition.

It will force them on the active partition on the second disk in this case. What happens if you use same entries and install to the first disk? How do you know that one is installing to first or second disk?

Quote

Yes, strange indeed, left+right arrow key do the up/down select work.

I recall something seen on boot-land about the nested config files, have to search a bit. If it's still up Monday will post there to see what Tinybit and the rest of the band have in mind.

Mind you, it's early stage. Other BIOSes may honor boot order and re-arange disk numbering. SATA/IDE mode may also matter.

[ilko_t]

ilko_t, on Jan 10 2010, 10:37 AM, said:

...Other BIOSes may honor boot order and re-arange disk numbering. SATA/IDE mode may also matter.

Quick proof- just tested on motherboard MSI G31M3, 2 SATA disks in IDE mode, no option for AHCI/SATA.
Upon changing boot order in BIOS, hard drive numbering changes too, no matter what port they are connected to, booting from USB using F11 hotkey.

[NT Man]

Wow, great. Now i have on one flash Windows 2003, Windows 7 and Windows FLP!!! Want also add Ubuntu Linux. Please make support for grub4dos Ununtu Linux feature.

[ilko_t]

NT Man, on Jan 10 2010, 10:26 PM, said:

Wow, great. Now i have on one flash Windows 2003, Windows 7 and Windows FLP!!! Want also add Ubuntu Linux. Please make support for grub4dos Ununtu Linux feature.

Meanwhile have a look here for Ubuntu, there are grub4dos entries for a few versions:
http://www.boot-land.net/forums/index.php?...=5041&st=20

[NT Man]

In the current version Grub4Dos already run Ubuntu, but loading fails due to wrong directory structure.

[ilko_t]

What did you exactly do?
You need to copy the ISO file manually and add the mentioned in that topic entries to menu.lst, according to Ubuntu version.

[wimb]

ilko_t, on Jan 10 2010, 07:37 PM, said:

It will force them on the active partition on the second disk in this case. What happens if you use same entries and install to the first disk? How do you know that one is installing to first or second disk?

The user will know where he wants to install and can select from grub4dos menu the TXT-mode start entry that is most suitable to his needs. So when you offer both strategies, then you can deal with most configurations.

[ilko_t]

Did you miss this post?

ilko_t, on Jan 10 2010, 12:31 PM, said:

ilko_t, on Jan 10 2010, 10:37 AM, said:

...Other BIOSes may honor boot order and re-arange disk numbering. SATA/IDE mode may also matter.

Quick proof- just tested on motherboard MSI G31M3, 2 SATA disks in IDE mode, no option for AHCI/SATA.
Upon changing boot order in BIOS, hard drive numbering changes too, no matter what port they are connected to, booting from USB using F11 hotkey.

How would an average user know what his BIOS does, in order to select the appropriate entry? Which one it would be? The one shifting all internal disks one position up and USB disk last, or the desired disk mapped to hd0?
One likes to manage boot via a boot loader, other prefers to use BIOS boot order.

This is going to be a little mess, I'd stick with the default Setup behaviour, whatever BIOS provides as first internal disk, boot files go there. This is also well known and documented behaviour. Next would be Vista/7, behaviour is the same. There we cannot manipulate it, for now.

An advanced user willing to take the other disk out of the equation should disconnect or disable that disk during setup, or amend entries manually. This goes to the help files.
I 'd now rather focus on more important things to fix and add

[jaclaz]

ilko_t, on Jan 11 2010, 09:14 AM, said:

How would an average user know what his BIOS does, in order to select the appropriate entry?

Once ruled out Crystal balls, Tarots and I-Ching, not much remains.

Patterns of dust on hard disk covers? But it won't work for new systems.

Pig spleen has not proved as very reliable in other fields of prediction, AFAIK:
http://www.almanac.com/image/pig-spleen-we...rediction-chart




jaclaz

[wimb]

ilko_t, on Jan 11 2010, 09:14 AM, said:

This is going to be a little mess, I'd stick with the default Setup behaviour, whatever BIOS provides as first internal disk, boot files go there.

If someone has a computer running Windows 7 and someday he decides to place an extra harddisk and
will Install XP from USB-stick using small ISO method,
then booting from second harddisk will fail and booting with Windows 7 will fail (BOOTMGR BootSector is gone).

I thought may be it is possible to prevent such problems, allthough it is default Windows behavior.
But as you say, other things can be more important to fix and add.

This post has been edited by wimb: 11 January 2010 - 11:22 AM

[NT Man]

ilko_t, thank's for link.
Tested this grub config on desktop PC and netbook Asus Eee PC 900.

title Start ubuntu-9.10-desktop-i386.iso from partition 0
find --set-root /pmagic/ubuntu-9.10-desktop-i386.iso
map /pmagic/ubuntu-9.10-desktop-i386.iso (0xff)
map --hook
root (0xff)
kernel /casper/vmlinuz boot=casper iso-scan/filename=/pmagic/ubuntu-9.10-desktop-i386.iso quiet splash --
initrd /casper/initrd.lz
boot

Work very nice for me.

Have only problem with notebook Dell Vostro 1000.
Boot fail with this screen.



P.S. For Ubuntu 9.04 used initrd.gz, for Ubuntu 9.10 initrd.lz

[ilko_t]

@NT Man

I'd do the following:
- chkdsk on the USB disk
- compare MD5 sum for the ISO
- change in BIOS SATA mode to IDE/compatible, if possible
- test the memory modules, also by removing each of them if 2.
- look at Ubuntu's forum for hints, additional kernel parameters may get you going, start with the ones mentioned here, several are posted:
https://bugs.launchp...nux/+bug/172937
- ask for help in Ubuntu's forum

[NT Man]

Thank you, but the my problem seems in GRUB.
That the same image recorded on CD-R boot up normally on Vostro 1000.

This post has been edited by NT Man: 11 January 2010 - 12:34 PM

[ilko_t]

It could be also because you are starting it from USB, thus additional kernel parameters may be needed for this particular machine, or other factors, not present when booted from a CD may matter.
Sorry, I have no other hints, you've got plenty of them to try in the referenced link.

And by the way, to be technically correct- it's Grub4dos, not GRUB, although grub4dos developers are also actively participating in GRUB2 developing

[Nic303]

Avast found virus in archive...

Attached File(s)

•  A.jpg (50.12K)
  Number of downloads: 7

[ilko_t]

For some reason AV vendors quite often falsely detect virus patterns in AutoIt compiled programs.
When in doubt check online using multiple scanners:


I'd click on the link you have "Reports as false positive..."

[ilko_t]

wimb, on Jan 10 2010, 04:58 AM, said:

...

ilko_t, on Jan 10 2010, 11:40 AM, said:

Added:[/b] BTW- did you encounter the same behavior with the arrow keys while in winsetup.lst menus?

Yes, strange indeed, left+right arrow key do the up/down select work.

So I did see it somewhere, but not on boot-land

README_GRUB4DOS.txt

Quote

The following commands are boot-sensitive(and others are not boot-sensitive):

boot
bootp
chainloader
configfile
embed
commandline
halt
install
kernel
pxe
quit
reboot
setup

An unbootable title will be skipped when the user presses the Up Arrow or Down
Arrow keys. Even the unbootable menu item can get accessed(and executed) by
using the Left Arrow and/or Right Arrow keys.

We do have configfile in winsetup.lst, but it's conditional to geometry(hdX) result, hence it seems ignored.
Add "boot" as last line in each menu and everything goes back to normal:

Quote

title First part of Windows XP Professional SP2 setup from partition 0
root (hd0,0)
map --mem /WINSETUP/XPpSP2.ISO (0xff)
savedefault 2
geometry (hd9) && configfile /BOOTWS/10.lst
geometry (hd8) && configfile /BOOTWS/9.lst
geometry (hd7) && configfile /BOOTWS/8.lst
geometry (hd6) && configfile /BOOTWS/7.lst
geometry (hd5) && configfile /BOOTWS/6.lst
geometry (hd4) && configfile /BOOTWS/5.lst
geometry (hd3) && configfile /BOOTWS/4.lst
geometry (hd2) && configfile /BOOTWS/3.lst
geometry (hd1) && configfile /BOOTWS/2.lst
boot

[Nic303]

Boot part is ok but when Windows setup starts cannot copy files.

This post has been edited by Nic303: 15 January 2010 - 07:33 AM

[ilko_t]

You will have to be more specific.

[Nic303]

ilko_t, on Jan 15 2010, 11:16 AM, said:

You will have to be more specific.

Working now (although i make the stick using the same iso image)
Thanks.

This post has been edited by Nic303: 15 January 2010 - 11:03 AM