108 replies to this topic

[JoshuaCL]

Thanks for the dos4grub stuff.

I kind of felt that the expresscard wasn't going to be seen in dos since the device isn't bios capable (at least with my bios). I was trying to see if a simple fdisk would see it, I haven't gotten around to that yet, but I really don't expect it to.

correction, just tried it with fdisk, doesn't see it (doesn't see my sata drive either). Just sees the flash drive (go figure)

I did the suggestion for dos4grub, I get "file not found" when running the 1st command.

This is running from win7rescuepe grub4dos vs chainloading off of grub2.

I'm out of order because I'm a newb, and I have never tried to configure grub until yesterday, and I didn't have any feedback for the 1st 4 hours of trying stuff out. I'm actually kind of proud of myself for navigating linux, became a bit more proficient.

[Wonko the Sane]

It's grub4dos, NOT dos4grub.

Of course it cannot find the grub.exe file, unless you place it somewhere (in the root of same device where grub2 is) or use an explict path to it.

I do understand that you are trying to do your best (and you are doing it ) but it is very difficult (please read impossible ) to follow your progresses and to try and help you (if needed), from experience I can tell you that doing semi-random attempts usually results NOT in something working or it takes a lot more time when compared to do the tests with an order and "plan".

Right now I am completely lost on what you are trying to do, booting from what device with which bootloader, attempting booting what, etc., etc., if you take some time and post a description, maybe I can contribute something, or at least someone else may be able to do so.


Wonko

[JoshuaCL]

Yep, it also means that you may have read this thread, but have missed the main significance of it (having the services active in order to boot a NT based system from it) AND you are doing a lot of things together, mixing this and that in no apparent order.

Let's try making it with some order, OK?

All projects on boot-land DO NOT use GRUB, but rather grub4dos, which is what you should test.

The blinking cursor with grub2:


should mean that there is a problem in the bootsector.

using the "same method" with GRUB doesn't make sense, as the (ata8,1) iin GRUB is the same as "a suffusion of yellow".

From grub2 you should be able to chainload directly grub4dos:

linux16 /grub.exe

http://www.boot-land...showtopic=10276
once in grub4dos try:

find --set-root /io.sys

root

chainloader /io.sys

boot

obviously do the above manually on command line and post results.

Compare with the (already given link):
http://www.911cd.net...showtopic=20314

This (if it works) should solve the problem for Win9x DOS, and should be able to give us some more details on how the device is seen.
If you can "shortcut" and take grub2 off the equation, using directly grub4dos, even better.


jaclaz

I tried one more time, this time putting the grub files onto the xpresscard and chainloading from grub2 to grub4dos
grub loads, but that command produces file not found

I can see ntldr files by running ls (must be seeing my ata drive where winxp placed ntldr from trying to install xp onto the expresscard and putting the boot files on an ata device)

I'm thinking it dropped the ssd once it loaded grub because it can't see non-bios devices. The files it's seeing with the ls command is what's on another bios capable hd. Any way to peruse devices like in grub2?

[JoshuaCL]

https://answers.laun...question/103990

To add support for my SSD I need to:
1) write phison into file /etc/initramfs-tools/modules: echo phison >> /etc/initramfs-tools/modules
2) add it to the initrd: update-initramfs -c -k 2.6.31-14

[JoshuaCL]

all i have to say is wow, wtf

this is a pain in the ass

12+ hours and this is a constant reminder of why I hate and love computing at the same time

only problem is, once I realize it's solution I'll forget it, so 8 months down the road when I need it, I'll search for it again

http://ubuntuforums....d.php?t=1205674

[filipes]

Hi,

I have a Lenovo SL500 notebook and I am wondering if I am able to boot Windows XP from ExpressCard SSD disk (using internal PCI-Express bus) or maybe later try to boot from Firewire 800 external disk connected via ExpressCard. My notebook's BIOS doesn't support boot from ExpressCard.

I searched internet and also read this thread and as I understand, nobody was able to do it so far.

My question is: Is it possible? Is it worth to try it? Should I buy the ExpressCard SSD disk and try to experiment?

Please note: I am not a geek, just a higher level power user, so I would need some support from the community...

[Wonko the Sane]

I searched internet and also read this thread and as I understand, nobody was able to do it so far.

My question is: Is it possible?

Yes/No.
http://homepages.tes...no-answers.html

You understanding is correct, so what is the point of asking if it is possible where noone managed to do it?

My personal guess is that IT IS possible, but the way to do it was not found (yet ).

Is it worth to try it? Should I buy the ExpressCard SSD disk and try to experiment?

That's entirely up to you.

Please note: I am not a geek, just a higher level power user, so I would need some support from the community...

Comeon, this thread is about people trying to do it and disappearing after the first difficulties, there is no problem in support from the Community, there are lots of problems in will and perseverance by the asking member.

So, the whole point is if you are really game for it, rest assured that people will try and help you where possible.

Which doesn't mean that the attempts will be successful, it only means that we will all have some fun while attempting doing it.


Wonko

[filipes]

Ok, thanks for quick response.

I decided now first to try to practice booting Win XP from USB drive and later I will move to ExpressCard.

[JoshuaCL]

I've got a huge update for you guys.

Although, it's not entirely booting from Expresscard, it might just work.

Try putting on your bootable HD all windows files
mount your program files and such to the ssd

The essential windows folders that need to stay on the hdd seem to be
c:\windows\*.*
c:\windows\inf
system32
syswow64
assembly

the rest can move

I've tested this with my ssd and moving certain files to a raid volume using mklink.

I have a script that moves files over 512KB to my Raid, but I had to learn the hard way that I couldn't touch certain windows folders because it couldn't see the "raid volume" until after a certain point in the boot process.