Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

A Multiple Partition USB Stick with Multi Boot OS

- - - - -

  • Please log in to reply
80 replies to this topic

#51
Andrews

Andrews

    Newbie

  • Member
  • 32 posts
  • OS:Windows 7 x64
  • Country: Country Flag
Thank you so much jaclaz. You don’t only know a lot from what I can see, but you also care to supply precise, useful and detailed information. I haven’t tried it yet for lack of time, but when I do it I’ll post the result.
The more I deal with people, the more I love my dog. - Oscar Wilde.


How to remove advertisement from MSFN

#52
Andrews

Andrews

    Newbie

  • Member
  • 32 posts
  • OS:Windows 7 x64
  • Country: Country Flag
I followed the Stage 1 of the tutorial on the first post of this thread, step by step, completed with the links you provided and using first the Hitachi files, but it didn’t work. I used Paragon for partitioning because Windows never recognises more than the first partition and wants to format anything else with the total size of the stick, but not even starting to do it and giving an error if tried, not being able to do it. I have Windows 7 and I wonder if someone has already tried partitioning with this OS, because everything I read until now is with XP only.

Then, I tried with Anton Basov’s files, which you also mentioned, Same negative result.

Then, I attempted with BootIt v1.07, but strangely the USB drive does not even show up on the app window and sees negative capacities for the hard disks! Why!?

Then, I used WinSetupFromUSB-1-0-beta6, as mentioned on another thread of these forums. It could partition and format, but the result was again the same as at the first trial.

I think the problem is strictly on making Windows recognise the USB flash as a fixed drive. On Device Manager the stick is listed with the hard disks and labelled as Local Disk USB driver, but that means nothing; it is just parroting what it is instructed to display on the corresponding .inf file entry. I can also find the .sys, .inf, and .pnf files on the usual places, the ...\System32 directory and subdirectories. Still, it doesn’t work. :(

To finish, I did as recommended on another thread on this forum, using InstallStartDummyDisk.cmd, and added a new partition with Paragon, because at that point Windows Disk Manager wanted to make a logical or dynamic partition and I wanted a primary one. It worked :lol:, but when I reboot or remove and reintroduce the USB flash it is very seldom recognised, and the icon on explorer is not like a fixed drive. However, Windows does not propose formatting of any driver, only scanning and correcting errors, and when accepted it finds nothing wrong. It seems to be a mixed behaviour. I tried InstallStartDummyDisk.cmd, but then it was not accepted saying that “The specified service already exists”: So I removed the service with StopRemoveDummyDisk.cmd and rebooted as recommended. Applied InstallStartDummyDisk.cmd once more and it became OK, and the drives icons on explorer were again those for the fixed sort. Both have also the Recycle.Bin. I checked also for the System Volume Information at System Properties /System Restore. They are there when the system takes them as fixed. Strange, only the second partition is not in alphabetical order. :wacko:

I think it is not completely OK because on Device Manager there is only one Local Disk USB driver, and the properties include the options for Quick removal and Better performance not offered for fixed drives. I don’t know yet what will happen when I reboot or remove and put it back. I don’t want to delay this description for too long and I can’t try it now. I’ll do all that later, but I don’t think it will be much different from what happened before.

I wonder, what will be wrong in all of this. What am I missing? :blink:
The more I deal with people, the more I love my dog. - Oscar Wilde.

#53
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,036 posts
  • OS:none specified
  • Country: Country Flag

I wonder, what will be wrong in all of this. What am I missing? :blink:

Basically, you are trying to adapt an oldish solution to a newish, DIFFERENT OS, and guess what?
Result is DIFFERENT.

AFAICR Windows 7 had not one problem in the world in partitioning a drive marked as removable through diskpart, last time I checked.

Now that you have verified empirically that applying changes to a given set of instructions may not always work, if you explain WHAT you are willing to do/create (as opposed to HOW to do/create it) I may give you some more suitable links/advice.

Personally, since I hate all this mess with "Removable" vs. "Fixed", I tend to "flip the bit" in the hardware, whenever possible, and be done with it, as you may have found out in the thread you are referencing.


jaclaz

P.S.:
Just to keep things as together as possible it seems like SPFDISK has a new home (and a much newer version - March 2009):
http://spferng.myweb.hinet.net/
thanks to halohalo:
http://www.msfn.org/...c=105936&st=487
Info is quite readable with google translate:
http://translate.goo...en&hl=&ie=UTF-8

Edited by jaclaz, 16 May 2010 - 12:28 PM.


#54
Andrews

Andrews

    Newbie

  • Member
  • 32 posts
  • OS:Windows 7 x64
  • Country: Country Flag

Basically, you are trying to adapt an oldish solution to a newish, DIFFERENT OS, and guess what?
Result is DIFFERENT.

Yes, you are perfectly right and I am consciously trying to do it just because after so many and many hours searching I couldn’t find a more recent way to do it.


AFAICR Windows 7 had not one problem in the world in partitioning a drive marked as removable through diskpart, last time I checked.

How is that? I have not been able to create a second partition with diskpart, it refuses. This is the error I received when I try:
"No usable free extent could be found. It may be that there is insufficient free space to create a partition at the specified size and offset. Specify different size and offset values or don't specify either to create the maximum sized partition. It may be that the disk is partitioned using the MBR disk partitioning format and the disk contains either 4 primary partitions, (no more partitions may be created), or 3 primary partitions and one extended partition, (only logical drives may be created)."


Personally, since I hate all this mess with "Removable" vs. "Fixed", I tend to "flip the bit" in the hardware, whenever possible.

I too, strongly believe what you say and to be the best and more appropriate way would be as you put it and I wanted, but to FlipRemovableBit with BootIt v1.07 is not possible for me because, as I mentioned, the USB drive does not even show up on the app window and it sees negative capacities for the hard disks. (Is there a reason for these two errors that could be corrected?) So, how would you recommend me to do it forgetting the old methods for a newer OS, please? You do know a lot, maybe you could help me here. I hate to make you uselessly waste more time with this. There must be a solution as for the older OSs that I can't find.

Actually, I had already found this Chinese link. I did download that executable file, but all it does is to open a completely blank and not workable command line window. I also downloaded other versions from the same page and got the same result, I don’t know why. Furthermore, sorry, I could understand almost nothing with Google translate, but just technical terms like partition, boot manager, MBR, MS-DOS, hard disk, and others the like. As I already have difficulty reading non proper English (not my mother tongue), for me it looks like a heap of senseless words from which that I can’t even get the meaning.

Please, see the latest results described below. I was going to update my last post, but now that I found yours it goes here. All I want to do is to make a partitioned USB flash with two or three bootable partitions plus another one not needing to be bootable. Almost the same as on the tutorial of the staring post of this thread, but I can't make work with Windows 7. It seems to be very easy when I read the old posts, the only problem being as you put it at the beginning of your post: “trying to adapt an oldish solution to a newish, DIFFERENT OS”.

- - - - - - - - - - - - - - - - - - -

Here are the mentioned results no longer useful, which only interest is telling anyone else not to repeat the mistake:


Confirmed that the second partition on the flash drive is no longer available after rebooting. On Device Manager the under Disk drives, the Local Disk USB driver is still there with the Quick removal and Better performance options, but now the first partition is listed under Portable Devices without the Quick removal and Better performance options.

On Computer Management the stick looks as before, but the second partition only displays the size. When right clicking both have the options Extend Volume and Shrink Volume blanked. On the second, if we choose Change Drive Letter and Paths..., we get a long text error starting by The operation failed to complete because the Disk Management console is not up-to-date. Refresh... Close the Disk Management console... or restart the computer. But refreshing or closing and reopening don’t change anything. Neither does rebooting.

Exactly the same is observed when the computer is rebooted both when the second partition is recognized, and after having dismounted with StopRemoveDummyDisk.cmd.

I know this is silly, but a bad solution was perhaps to have two batch files, one to apply StopRemoveDummyDisk.cmd at shutting down clearing the hack, and a second one to submit InstallStartDummyDisk.cmd at start up. Of course, this would work, but was obviously not a solution, not even recommendable, and would delay both shut down and start up times.

The result is very disappointing because without this issue fixed nothing else can be done.

Edited by Andrews, 17 May 2010 - 03:04 PM.

The more I deal with people, the more I love my dog. - Oscar Wilde.

#55
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,036 posts
  • OS:none specified
  • Country: Country Flag
I am not at all "current" with Windows 7, it is well possible that it doesn't work as I remember, and as you describe. :unsure:
I would try, after having created the first partition of a given size, to hide it, disconnect and re-connect the stick, then try creating the second one.
I am sure that only one partition can be accessed/mounted at a time in any Windows NT, unless the filter driver is installed, but if you each time you hide the "other" you should be able to choose which partition to access.

However, I would separate the problem in two:
1) use the filter driver
2) try flipping the bit

1)I don't know if cfadisk.sys or dummydisk.sys are installable on Windows 7.
If they are, it is possible that you have some "wrong" settings in cfadisk.inf (or corresponding files).
You can try using this way:
http://www.911cd.net...showtopic=22795
which is a "generic" not "specific stick" way to have the filter working.
Most probably you need to disable driver signing, but cannot say.

If the filter driver approach doesn't work, you can always use manual partitioning of the stick, by using an image of it and/or a VM, but let first see if the cfadisk can work.

2)Maybe there is some misunderstanding.
If you click here:
http://www.mydigit.c.../ChipGenius.rar
you should get a chipgenius.rar file, open it in 7-zip (or winrar) and extract from it the files:
ChipGenius.exe
Chips.wdb
double click on chipgenius.exe, it is a GUI tool.
Close it.
Insert your USB stick.
Re-run it.
Select in the list in the upper window the USB stick that should be detected.
Read in the lower window what Chipgenius knows about it.
Post this latter info.

I can try helping you find the appropriate "Manufacturer tool (if any available).

jaclaz

#56
Andrews

Andrews

    Newbie

  • Member
  • 32 posts
  • OS:Windows 7 x64
  • Country: Country Flag
Hello jaclaz,

Thanks to your instructions I can finally use the USB flash drive as basic volume. I used the method with the REG file on your link to the 911cd.net site. Now, I can finally proceed with the other things I said I wanted to do. After all, it was not as you said: “I am not at all "current" with Windows 7”. You may not know as much as about other subjects, but you do know more than enough.

I had already made other deceptive trials before, but I don’t think it will be useful to post them here even if for the record. I think the other older methods do not work with Win7 as you supposed. I had already passed on that page when looking for the xpfildrvr1224_320.zip download, but I dropped it because the two links for that file are broken and I didn’t go back. It is a well written, well detailed and easy to follow tutorial by someone who knows what he is talking about.

- - - - - - - - - - - - - - - - - - - -

Just to answer some parts of your last post.

I had done just as you said after the emoticon, but without success.

I don’t know whether cfadisk.sys or dummydisk.sys were installed or not, but I do know that they were there and Windows created some files for backing the up as I described on my last post with names like cfadisk.inf_x86_neutral_86e982a1aa90238f and cfadisk.PNF.

However, dummydisk did not create that files. Soviet_direct_hooking_src.zip does not contain any INF file. What I know for sure, is that the drivers that we can see on Device Manager / Properties / Driver tab of the USB device are the same as for the other drives, before and after installing the hack. Maybe it is right.

I tried something else. As dummydisk does not have an INF file, and dummydisk.sys and cfadisk.sys are of different sizes, I changed the name of cfadisk.inf to dummydisk.sys to install it the same way and put it together with the dummydisk files. The result did not change from the previous experiences with the cfadisk files. I must point out that I was trying to hit something in the dark!

I used the ChipGenius app, but it doesn’t give much information aside from serial number, device type and PnP Device ID: VID = 0951 PID = 1624, but now there is no longer need to post it.

- - - - - - - - - - - - - - - - - - - -

I have made so many searches and read so many things that I don’t know how I was starting getting confused. After all, this is very silly because Windows could well have included this possibility in the system. All they have been doing for sometime are gimmicks to attract dumbs. See this thread example, which it is not the only one:
http://social.techne.../?prof=required
Started on 29th January, 2009, and still active.

OK, many thanks again for the very useful and kindly offered assistance.
The more I deal with people, the more I love my dog. - Oscar Wilde.

#57
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,036 posts
  • OS:none specified
  • Country: Country Flag

Thanks to your instructions I can finally use the USB flash drive as basic volume. I used the method with the REG file on your link to the 911cd.net site. ..... It is a well written, well detailed and easy to follow tutorial by someone who knows what he is talking about.


I take this for a final confirmation that Anton Bassov's dummydisk.sys with the approach that online so nicely detailed:
http://www.911cd.net...showtopic=22795
works allright under Windows 7. :) (Did I get it right? You don't mention which driver you finally installed. :unsure:)

However, if dummydisk.sys works, also cfadisk.sys should work with the generic method by cdob, if you hava an occasion to try again it, please report.

I don’t know whether cfadisk.sys or dummydisk.sys were installed or not, but I do know that they were there and Windows created some files for backing the up as I described on my last post with names like cfadisk.inf_x86_neutral_86e982a1aa90238f and cfadisk.PNF.

Yes, most probably you did not manage to intall them correctly or fully.

I tried something else. As dummydisk does not have an INF file, and dummydisk.sys and cfadisk.sys are of different sizes, I changed the name of cfadisk.inf to dummydisk.sys to install it the same way and put it together with the dummydisk files. The result did not change from the previous experiences with the cfadisk files. I must point out that I was trying to hit something in the dark!

Writing .INF files is tricky business, you have probably missed some bit.

I used the ChipGenius app, but it doesn’t give much information aside from serial number, device type and PnP Device ID: VID = 0951 PID = 1624, but now there is no longer need to post it.

Well, that's enough:
it seems like a kingston using a SSS chip:
http://www.flashboot...es&op=cat&id=17
http://translate.goo...en&hl=&ie=UTF-8
most probably a SSS6690
(just in case yu want to take the HARD :ph34r: way)

OK, many thanks again for the very useful and kindly offered assistance.

You are welcome. :)

jaclaz

#58
Andrews

Andrews

    Newbie

  • Member
  • 32 posts
  • OS:Windows 7 x64
  • Country: Country Flag
OK jaclaz, I thought I had explained properly, but now I see I might have not, sorry.

I followed strictly and only the tutorial by online on your 911cd.net link, the method that uses Anton Bassov’s files, the only one in the tutorial using a .REG file, not the other method with the "xpfildrvr1224_320.zip" folder. The driver I copied to "system32\drivers" was "dummydisk.sys" renamed as "dummy.sys". I didn’t do it completely because I stopped before installing "grub4dos". This online’s method on 911cd.net works perfectly with my USB flash on Windows 7.

Once this worked as desired, I did not try anything else and I did not try to install the “cfadisk.sys” driver. I cleared all cfadisk files from the sustem. Therefore, it may work as well as "dummy.sys" does, but I can’t confirm that without trying. Do you want me to uninstall "dummy.sys" and the .REG hack, and try “cfadisk.sys”. I can do the experiment as a contribution. Please state it.


Yes, most probably you did not manage to intall them correctly or fully.

I put all the files in the same directory. Through Device Manager, on the drive Properties, Driver tab, I updated the driver by directing Windows to the directory with the files. This is the usual way I know unless hacking the system.


Writing .INF files is tricky business, you have probably missed some bit.

That’s right, but all I did was to copy the flash ID to a specific place that I found to be the same in different tutorials. I don’t know. This is exactly the only line I changed: %Microdrive_devdesc% = USBSTOR\Disk&Ven_Kingston&Prod_DataTraveler_G2&Rev_1.00

Here is the ChipGenius report result that you seem to want. I didn’t find much utility on this because there are too many missed lines. I think this is the one that corresponds to the flash:

Device Name: +USB Mass Storage Device

PnP Device ID: VID = 0951 PID = 1624
Serial Number: 0013729982D5F9A0B6320C31
Revision: (Information not returned)

Device Type: Standard USB device - USB2.0 Full-Speed (USB1.1)

Chip Vendor: (No match record)
Chip Part-Number: (No match record)

Product Vendor: USB
Product Model: Mass Storage Device

Tools on Web: (N/A)


It is a Kingston Data Traveler G2 v1.00 (Yes, there is an original spelling error, it is everywhere and I used it as is on the .INF file.)
I didn’t understand the “(just in case yu want to take the HARD :ph34r: way)”. What is that? Can you tell me what you want me to do with this, please?

Thank you again jaclaz.
The more I deal with people, the more I love my dog. - Oscar Wilde.

#59
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,036 posts
  • OS:none specified
  • Country: Country Flag

Do you want me to uninstall "dummy.sys" and the .REG hack, and try “cfadisk.sys”. I can do the experiment as a contribution. Please state it.


Yes, please :) (this way we have a final confirmation for cfadisk.sys also).


all I did was to copy the flash ID to a specific place that I found to be the same in different tutorials. I don’t know. This is exactly the only line I changed: %Microdrive_devdesc% = USBSTOR\Disk&Ven_Kingston&Prod_DataTraveler_G2&Rev_1.00

Yep, that's the "old" way (and prone to errors/inconveniences, as you "attach" the filter to a specific hardware device).
The new "generic" way by cdob simplified and examplified in the referred to thread by online:
http://www.911cd.net...showtopic=22795
should be (please read as "is") more tolerant, as you "attach" the filter driver to the whole "USBSTOR\GenDisk" it should/will work for ANY USB stick, see the original post:
http://www.msfn.org/...ic=126868&st=12

Here is the ChipGenius report result that you seem to want. I didn’t find much utility on this because there are too many missed lines. I think this is the one that corresponds to the flash:

No, sorry for the misunderstanding, the Vid and Pid you had already posted was enough to find the (supposedly) "right" tool for it. :)

I didn’t understand the “(just in case yu want to take the HARD :ph34r: way)”. What is that? Can you tell me what you want me to do with this, please?

That was referred to eventually risk using on your stick the linked to Manufacturer's Tool to "flip the bit" of the controller.
As said, this - if possible with that tool - is the most "definitive" way, but it implies some risks of "botching" the stick for good.
Thus I can "recommend" it as the "right" thing to do (in the sense that you won't have anymore ANY problem with Fixed vs. Removable under ANY OS/install, without needing EVER to reinstall the filter driver), but cannot actually "recommend" doing it :ph34r:, as it involves the said risk, and don't want to be "held responsible" ;) for accidentally ruining someone else's stick permanently.
I personally "flip the bit" of all my sticks, but never used that particular Manufacturer Tool, so, I cannot even say if it allows doing it, let alone know if it's "friendly", "easy" or not, it's all up to you.

More generally, my personal approach is somewhere between :angel :

If ain't broke don't fix it

and:

Life is "trying things to see if they work"

it's your choice, you only know if you have the experience, knowledge, and ultimately "guts" to risk doing a firmware change, after having judged if you need it at all or if you are happy with the filter driver. :)


jaclaz

#60
Andrews

Andrews

    Newbie

  • Member
  • 32 posts
  • OS:Windows 7 x64
  • Country: Country Flag


Do you want me to uninstall "dummy.sys" and the .REG hack, and try “cfadisk.sys”. I can do the experiment as a contribution. Please state it.

Yes, please :) (this way we have a final confirmation for cfadisk.sys also).

I Deleted dummy.sys from the system. There was only the one I dropped in "system\drivers" in the whole system. I extracted the UFD and rebooted. I reintroduced the flash and wasn't any difference, just as if installed. Then I deleted the dummy key in the registry that had been merged with the dummy.reg file. No difference whatsoever :(. The two partitions continue to appear on Computer Management as basic disks, which is with all their options including expanding, shrinking and partitioning. This is not inconvenient for me because that is the way I want it to be :D, but I can't try to install "cfadisk.sys" as it is. I searched the registry for other entries, but I don't know enough to start deleting other entries blindly in the registry :w00t:. If you know of another way to proceed, please tell me how.


Yep, that's the "old" way (and prone to errors/inconveniences, as you "attach" the filter to a specific hardware device).

Right, I was telling about the previous experience that always failed for me, not the one on http://www.911cd.net...showtopic=22795, which was a complete success.

About trying the risky "flip the bit" business. I do need more information before deciding. I understand the worst that can happen is to say good bye for good to my flash drive :(, that is no one’s death but losing my money :angry:. I tried to understand something on the russian link you provided, thanks. I could see that with Vid and Pid you could find the Manufacturer's Tool, but I wasn’t able to find that. I avoid russian and chinese sites because I often feel lost; many also have viruses, but that I can manage with protection. Please tell me something more about that and how it is done, so I can try investigating further and decide. I think this will take me some time :unsure:.
The more I deal with people, the more I love my dog. - Oscar Wilde.

#61
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,036 posts
  • OS:none specified
  • Country: Country Flag
Well, what you report seems more like I remembered it. :unsure:

If I were you, I would leave everything "as is", and wait to do further tests when you happen to get another stick that doesn't work as you want it to. :)

About the "hard way", the link I posted is a direct link to page where actual "Manufacturer Tool" that are (or better should be) appropriate for your stick.
You download one, and you try running it (WITHOUT the stick connected).
You try and see if there is an option (they do have an english interface) that *resembles* what you want to do.
IF there is (not *ALL* controllers or not *ALL* utilities have this feature) you try it.
Now you do understand why the :ph34r:, don't you? ;)

Some utilities are "easy", some are "difficult", it is more a gambling game than anything else.

So, DO NOT do it.

If you are curious, just download them and try running them with NO devices attached, to see how they "feel".

You are now a happy bunny in the basket :), don't make things that may make you become a depressed one ;).
http://www.msfn.org/...ic=128727&st=10

jaclaz

#62
Andrews

Andrews

    Newbie

  • Member
  • 32 posts
  • OS:Windows 7 x64
  • Country: Country Flag
After the third reboot after having deleted dummy.sys and the corresponding sub key in the registry the hack stopped. Strange it did not happen immediately after the first reboot :lol:. I just reinstalled it again. This is just for the record.

I found the USB6690 app because you named it on your post. After investigating, I concluded that it was exactly the one for my stick, but it was also not easy to find the download button :o. This is why I said I avoid Russian and Chinese sites, annoying, frustrating and most of all an enormous waste of time :boring:.

I’ll do as you say :yes:, live it as is for the time being. For now it is what I need and was looking for :). I am not going to use it on other computers, at least for now. Soon I’ll have more sticks, even because all disks tend to be replaced by chips. Hard drives will still be too expensive for quite some time, but smaller sizes are more affordable and convenient. CDs and DVDs have already started disappearing.

I looked at the USB6690 GUI, but couldn’t find any “All” reference, and the settings have too many things. They are in English, but I don’t understand most of them, and because I’ll need to know much more we better talk about that when the time comes. For now I stick with what I have :thumbup.

Thank you for everything.

Attached File  USB6690.jpg   153.81KB   28 downloads


The more I deal with people, the more I love my dog. - Oscar Wilde.

#63
Andrews

Andrews

    Newbie

  • Member
  • 32 posts
  • OS:Windows 7 x64
  • Country: Country Flag
Hello,

I want to announce that I tried the other hack version of online's tutorial at http://www.911cd.net...showtopic=22795, which he mentions as another “alternative way”. This one uses the Hitachi drive in xpfildrvr1224_320.zip, and an hm directory containing the decompressed files with a modified cfadisk.inf file is placed in “system32\drives”. It does not use any registry .REG file as on the Anton Bassov' version.

Before applying this Hitachi drive hack just to try, I had to remove Anton Bossov’s hack (the added registry key and dummy.sys in “system32\drives”), which was working perfectly :yes:, and rebooted.

This Hitachi drive hack works as perfectly as the online's Anton Bossov version. :thumbup

Note: I had already tried to do this, but after having performed the above mentioned removals and rebooting, the PC kept showing the old removed driver even with everything deleted :thumbdown. I can’t explain this, and at the moment I didn't have the time to insist.

Reading through following online's links, I acknowledged the existence of many BIOS-USB related problems when booting from USB :realmad:. Even if not exactly the same sort of problem, with my present BIOS there is something strange when booting with an USB flash connected (with or without hack): it invariably boots from USB regardless of how I had set the BIOS :crazy:. Checking up the BIOS settings while booting in these conditions, I see that they have set themselves differently: the hard drives are not shown on the booting options and the booting order is now USB, DVD. Only, nothing else, unchangeable, when I have also three hard disks and a CD :wacko:.
The more I deal with people, the more I love my dog. - Oscar Wilde.

#64
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,036 posts
  • OS:none specified
  • Country: Country Flag
Yep it's BIOS related.

Also, some motherboards have a hot-key to change booting order on-the-fly at boot time that behaves sometimes differently/strangely from what happens if you change the booting order inside "real" BIOS page.

Most probably you can work around the issue by using grub4dos to re-map drives before booting the OS.
Typically:
title boot from internal HD
map (hd0) (hd1)
map (hd1) (hd0)
map --hook
root (hd0,0)
chainloader +1

You will need to check in grub4dos command line if it sees the internal hard disks (it should).

To start playing with it start here:
http://diddy.boot-la...os/Grub4dos.htm
You may also want to try using methods #1 or #3 (chainloadeing from windows)
http://diddy.boot-la...all_windows.htm
http://diddy.boot-la...ws.htm#windows1
http://diddy.boot-la...ws.htm#windows3

Read about command line:
http://diddy.boot-la...iles/basics.htm
http://diddy.boot-la...s/files/cli.htm

Then press "c" and type:
find
[TAB]
If you see something like:

(fd0) (hd0) (hd1) (hd2) (rd) (cd)

it means that the internal drives are seen nonetheless at BIOS level and you can re-map them.


Happy to know that also cfadisk.sys worked. :)


jaclaz

Edited by jaclaz, 22 May 2010 - 08:25 AM.


#65
Andrews

Andrews

    Newbie

  • Member
  • 32 posts
  • OS:Windows 7 x64
  • Country: Country Flag
:hello: Thank you for the links, I’ll read the tutorials.

I have a problem. When Windows 3.0 appeared I moved to Windows because it was funnier, but slowly I forgot the little I already knew about DOS, Linux and other interesting things :lol:, and now I am almost completely blank, a 0 :(.
The more I deal with people, the more I love my dog. - Oscar Wilde.

#66
3guesses

3guesses
  • Member
  • 1 posts
  • OS:XP Home
jaclaz

I don't know if you're still monitoring this thread, but if so I wonder if you could answer a question for me/point me in the right direction?

I came across this thread after buying an 8GB USB memory stick, with the intention of partitioning it off and making it bootable so that I could perform O/S installations from it instead of having to carry around a load of discs. However, after reading this thread I was wondering if there was a tidier solution: make the USB stick bootable and install a boot loader on it that had the ability to mount and boot an ISO image as a virtual CD/DVD (a bit like DAEMON Tools does for Windows). Then it would just be a matter of copying ISO images of the operating system installation disks onto the memory stick. Do you know if this idea is possible? I had a read of the GRUB wiki (I am more familiar with LILO), but I was none the wiser about whether or not it could boot an ISO image as a virtual CD/DVD and at the moment I can't afford to spend hours and hours trying things out unless I know that they will work.

Any help you can offer will be greatly appreciated.

BTW your English seems very good for an Italian?

Cheers,

3g

#67
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,036 posts
  • OS:none specified
  • Country: Country Flag

BTW your English seems very good for an Italian?

Interesting question, maybe you had some experience with a few "less fluent in English" Italians? :unsure:
I presume that the "average internet English" (written by non-British people) sounds a lot like "pidgin English" to the British (well actually a lot of American English probably does the same ;)), but don't think that average "Italianish" is in any way worse than "Portuglish", "Spanglish" or "Germanish" ....

I simply try to do my best in writing in English as it was taught to me (more years ago than I like to recall... :angel ) by an English mother-tongue teacher, I am sure she would be happy to know that all the time she spent with me wasn't entirely wasted. :yes:

However, after reading this thread I was wondering if there was a tidier solution: make the USB stick bootable and install a boot loader on it that had the ability to mount and boot an ISO image as a virtual CD/DVD (a bit like DAEMON Tools does for Windows). Then it would just be a matter of copying ISO images of the operating system installation disks onto the memory stick. Do you know if this idea is possible?

Sure it is possible :), only you are making it much easier (or rather too "one-size-fits-all") than it really is. :ph34r:
Take your time reading these TWO threads:
http://www.boot-land...?showtopic=8944
http://www.boot-land...?showtopic=5041

I had a read of the GRUB wiki (I am more familiar with LILO), but I was none the wiser about whether or not it could boot an ISO image as a virtual CD/DVD and at the moment I can't afford to spend hours and hours trying things out unless I know that they will work.

Here we have a problem, disambiguation needed:
  • GRUB is "GRUB Legacy", discontinued, has NOT ANY "special" provision for DOS, NT or .ISO mapping/booting
  • grub4dos is an evolution of #1, which ADDS "special" provisions for DOS, NT, .ISO mappping and many more
  • GRUB2 is now "GRUB" it is a COMPLETELY REWRITTEN bootmanager, with same features of #1, AND added .ISO mapping BUT NOT any "special" provisions for DOS, NT, and a number of other features grub4dos has.

What you want is NOT "GRUB", NOT "GRUB legacy", NOT "GRUB 2" but grub4dos:
http://www.boot-land...hp?showforum=66

Read AT LEAST (besides the two already given threads) the other "stickies", i.e. the WHERETO:
http://www.boot-land...hp?showtopic=14
AND the GUIDE (linked to here):
http://www.boot-land...?showtopic=5187

jaclaz

#68
sk8nfool

sk8nfool
  • Member
  • 1 posts
  • OS:none specified
  • Country: Country Flag
Nice tutorial. Unfortunately the link to xpefiles (http://www.xpefiles....wtopic.php?t=92) is broken. What was this pointing at?

Thanks

#69
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,036 posts
  • OS:none specified
  • Country: Country Flag

Unfortunately the link to xpefiles (http://www.xpefiles....wtopic.php?t=92) is broken. What was this pointing at?


Maybe had you spent a few minutes actually READING this thread before posting, you might have found yourself the answer, please READ these two (and possibly the WHOLE thread):
http://www.msfn.org/...os/page__st__48
http://www.msfn.org/...os/page__st__49

jaclaz

#70
zopfan

zopfan
  • Member
  • 1 posts
  • OS:Windows 7 x86
  • Country: Country Flag
I wish the topic was updated with latest scenario. I.e. Win7 and 4gb pen drive and other latest things. 2006 is rather too old to follow.

Alas!!

#71
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,036 posts
  • OS:none specified
  • Country: Country Flag

I wish the topic was updated with latest scenario. I.e. Win7 and 4gb pen drive and other latest things. 2006 is rather too old to follow.

Alas!!


Well, you can still READ the thread and maybe you will find liks to OTHER more modern ways/approaches, like, you know:
http://www.msfn.org/...os/page__st__40

jaclaz

#72
TheSeeker

TheSeeker
  • Member
  • 4 posts
  • OS:none specified
  • Country: Country Flag
I would like to try to modify the RMB.

But where can I find the right tool?

I have the following sticks available



PnP Device ID: VID = 0409 PID = 0058
Revision: 1100

Product Vendor: JetFlash
Product Model: Transcend 16GB


PnP Device ID: VID = 0409 PID = 0058
Revision: 1100

Product Vendor: OCZ
Product Model: RALLY2


PnP Device ID: VID = 090C PID = 1000
Revision: 1100

Chip Vendor: SMI(??)
Chip Part-Number: SM321~SM325

Product Vendor: Corsair
Product Model: Flash Voyager

#73
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,036 posts
  • OS:none specified
  • Country: Country Flag

I would like to try to modify the RMB.

You do know that it is RISKY business? :unsure:
You do know that it may make the stick inaccessible (if you do the wrong things with such a powerful tool)? :ph34r:

You are "TheSeeker", I am "The Finder", there must be a reason ;).

Try with the SMI only first:
http://flashboot.ru/...es&op=cat&id=10

You'd better go there through google translate:
http://translate.goo...=10&sl=ru&tl=en

In this particular case the answer is not 42 :w00t: but rather 320. :rolleyes:

The 0409:0058 doesn't sound "right". (it is a Vid/Pid for a USB hub)
Is what you posted the output of chipgenius?
http://reboot.pro/4661/
If not try again with it.

jaclaz

#74
TheSeeker

TheSeeker
  • Member
  • 4 posts
  • OS:none specified
  • Country: Country Flag
Thanks for the links. I will work through it.

And yes I know it's risky.
Recently I have moved to USB 3.0 and replaced all my everyday USB sticks with faster ones.
So if the old ones get corrupt so be it.

Yes the data is from chipgenius.
Ah the devices are listed twice. Once with their assigned drive letter and once without it.

This are the correct values.

PnP Device ID: VID = 8564 PID = 1000

and

PnP Device ID: VID = 0324 PID = BC08

#75
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,036 posts
  • OS:none specified
  • Country: Country Flag

This are the correct values.

PnP Device ID: VID = 8564 PID = 1000

and

PnP Device ID: VID = 0324 PID = BC08

This:

PnP Device ID: VID = 8564 PID = 1000

can be *almost anything*
See the results of searching here:
http://flashboot.ru/...php?name=iflash
most probably it is a "valid" VID/PID from TRANSCEND that can have "under the bonnet" *any* controller

This:

PnP Device ID: VID = 0324 PID = BC08

is *unknown*, the 0324 is OCZ, just like the 8564 above is Transcend, it is probable that it is an SMI chip as well (like the 090C/1000), but cannot say.

jaclaz




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users



How to remove advertisement from MSFN