Jump to content











Photo
- - - - -

Its not the fault from grub4dos that untouched windows-xp.iso`s can t boot - this is propaply wrong!?


  • Please log in to reply
41 replies to this topic

#1 livedude

livedude

    Member

  • Members
  • 83 posts
  •  
    Germany

Posted 24 March 2012 - 07:01 PM

first forgive me my bad english. i am relativ new to windbuilder and spend some some work in it.
i also had the goal, to make an multi-compilation.iso, with xp.iso for installation, chossable from the grub4dos-startemnu.
well i read much about it and one, i have forgot his nick, came to the conclusion, that untouched win-xp,iso can t word with grub4dos, becouse the microsofts way of booting them is fault and it should not be the fault of grub4dos.
well, i am no expert, but i don t beliefe this.
reason:
the untouched xp iso also works for example with virtualbox, or native as psyical medium in the cd/dvd-rom

neither!, virtualbox or if it runs native in the dvd-rom as burned iso, has a crack or modified code or something to let it run, but it works!
it only don t works with grub4dos. so i think the proplem is the method or something grub4dos handle this things.
if grub 4 dos would emulate everything 1:1 like the virtualbox cd/dvd-rom-driver/bios or whatever, or a psyical-medium wich is in the cd/dvd-rom does,
then it should also work, so i think, grub4dos make anything wrong, or it is just not able, to handle isos like an untouched windows-xp.iso.
for this reasons, i also don t beliefe that it should not the fault of grub 4 dos that these things are not working.
i think it is! the fault of gub 4 dos and nothing else.

regards
livedude

Edited by livedude, 24 March 2012 - 07:07 PM.


#2 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14758 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 24 March 2012 - 07:30 PM

Well, you have made three mistakes :ph34r: in a single post :w00t:, but it's allright :smiling9: you are new to the board (so welcome :)) and probably relatively new to the ways Windows and grub4dos and .iso's work, though you could try to keep tones a little bit more cool and avoid "accusing" *anything* or *anyone* of something before being very, very sure of what you are saying.

First thing the untouched XP .iso can work with grub4dos AND with a suitable driver (but of course cannot work with grub4dos ONLY, as it is OUTSIDE the scope of grub4dos).
Please do review this:
http://reboot.pro/8944/
At least TWO methods were developed to install windows XP from an untouched .iso:
http://www.msfn.org/...aded-iso-image/
http://www.msfn.org/...rom-a-iso-file/

Second, this has nothing to do with Winbuilder, we have a grub4dos section:
http://reboot.pro/forum/66/
where you should have posted (if the issue is grub4dos) and where you would have found the above considerations on grub4dos and NT based .iso's needing an external driver.
And there is an entire sub-forum on MSFN:
http://www.msfn.org/...ndows-from-usb/
dedicated to "Install Windows from USB" where you would have found the two methods linked to above.

Third, the arguments that you brought up to support your theory are invalid, as in a VM the .iso is actually mounted in an emulated CDROM drive, thus built-in XP CDROM drivers hook the emulated device.

:cheers:
Wonko

#3 livedude

livedude

    Member

  • Members
  • 83 posts
  •  
    Germany

Posted 25 March 2012 - 04:47 PM

Hi Wonko,

if this is the wrong section for this post, please move it where you think it belongs better. didin t know that. i am total know to this board.

Well, you have made three mistakes :ph34r: in a single pos


lets see...

the method to bring untouched xp to running with ramdisks has negative sideffects, if i have understood that right. you need much ram, becouse you must load everything in ram that it works. sure its better then to manipulate the orginal untouched iso, only that grub can start it (wich is horrible becouse of many possible negative sideeffects), but its far from beeing perfect becouse you need much ram to use such an ram-disk. my live-iso-.diagnostic,repair and so on- is-compilation, should need as less as possible ram for all tasks: starting live systen, installing windows and so on.


Second, this has nothing to do with Winbuilder, we have a grub4dos section:


not directly. i was looking for an way to create my ideal live-system. so i found winbuilder. i use the win7_pe_se project and saw that i have to modify scripts that it works for my needs:
exampe:
the other o.s-bootfloppy script. well, its not bad to have an posibility to implement bootdisks (.img images) sure, but what is much better, is a way to implement isos to the live system. so i modified that script that this worked for my needs. i saw that they use something called grub 4 dos wich makes the menues entrys and is responsible for starting isos and stuff. so i had to grapple with grub 4 dos, learning the syntax and how it start things. much work and i am still a bloody beginner, but i am far enough, that it works for my needs.
many isos like trueimage, redo-backup and stuff, i can now start directly from the bootmenu and so i must not start for all things the whole win7-live-system wich is also part of my iso-compilation.
as i tried to get also the untouched-xp.iso with grub4dos to start, i saw many entries from people with the same goal.
so far i understood that what i read correctly: its not the wish of the grub4dos devs to implement drivers and stuff, so that grub4dos can also start thsese untouched-xp.iso and of course many other things.
so its technicaly possible, but they wont it and becouse they want it not, grub 4 dos can t do atm technicaly not, becouse its not implementet.
i don t wana lose me in techincal details wich i don t understund full, but so the situation is looking for me.
but its no big suprise. i know it from many other oss-projects: the devs make just their own thing, don t care what many people want.
this is then the reason for forks. is grub 4 dos not also a fork of the original grub?
i don t want to offend anyone or anything, but out of my personal sentence this is ignorance of users needs.
for that reason, i make it like the most people: as long as there is no better alternative as grub 4 dos, i use it, but as soon as there is a alternative wich has the ability many people wana have, including me (in this case, build in driver or something that grub4dos can handle this things, don t wana loose me in technical details wich i also don t understund complette. the only important point is that it is technicaly possible!), am very quick away.


Well, you have made three mistakes :ph34r: in a single


so what keeps from that now? everything is only a thing of the perspective and viepoint you have.
atm grub 4 dos can t native handle this things (technicaly propably possible, but the devs don t want it), so am not completly wrong.
therefore i see no three mistakes:)

like i said, that is no offence or something, is just my personal sentence and i hope that its okay to say his personal sentence here without getting in conflicts. i don t wana come in trouble becouse only i am saying what i am thinking.
i am grown up and life in a democratical country so its normal for me to say the personal sentene without getting in trouble for that.
i wish you all a nice sunday.

greetings
livedude

Edited by livedude, 25 March 2012 - 05:06 PM.


#4 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14758 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 25 March 2012 - 05:14 PM

Well, as said, you might want to express your free opinions in a "softer" way :), but more than that try to separate opinions from facts.

If you are not "sure" because you do not understand completely something it is better if you try to understand it fully before expressing an opinion on it.

grub4dos is a bootloader/bootmanager (it's scope is to boot - and nothing else - it is not a driver)
As it was shown to you, in combination with a suitable driver it can work allright with "untouched" XP .iso.

In a carpenter's example, I read your post as:

This hammer is stupid because it cannot carve properly this wooden plank.

but the whole point is that hammers are not designed to carve wood, chisels are, and you need to use BOTH a chisel and a hammer if you want to carve wood.

And this is a technical board, where the technical part is very relevant, you cannot set it aside with "don t wana loose me in technical details wich i also don t understund complette", nor draw conclusions (like the ones about Virtualbox) without knowing first how things work "technically" and "in detail".

If the problem is:
"Can I use an untouched .XP iso?"
The answer to it is:
"Yes, by using grub4dos and one of the compatible drivers developed, either firadisk or winvblock might do."

If the problem is:
"grub4dos sucks because it cannot manage an untouched XP .iso without an external driver which is not part of the grub4dos package."
There are no answers AFAIK as it is not a problem.

:cheers:
Wonko

#5 livedude

livedude

    Member

  • Members
  • 83 posts
  •  
    Germany

Posted 25 March 2012 - 06:28 PM

Hi Wonko,

grub4dos is a bootloader/bootmanager (it's scope is to boot - and nothing else - it is not a driver)


and grub 4 dos can t do this goal (boot), for what it is concipatet, completly with all iso`s, becouse it lacks of a sutibale driver or something.
so what is gloser then as to impliment what this tool needs that it can successful handle its job?


i know that this is a technical board and therefore i am also lucky. i like this board becouse i found many helpfull informations in it.
but that its in this case not the point.

the point was, that grub is able from the technical side, to start these untouched xp and others iso`s native.
that it can do it, devs must implement a suitabe driver or something.
the exact technical details are not so important for me, becouse the only point is: it is technicaly possible and they don t do it.
if they don t do it for ideology reasons or other ones, wich is als not relevant for me, becouse its not changing the result.
atm grub 4 dos isn t able to do it, becouse the devs don t want it and have a other focus, scope or whatever.
that was the point becouse i said, i don t want to go in technical details, wich i first don t understund completly, and more important: wich don t change anything on the point i said.


If the problem is:
"grub4dos sucks because it cannot manage an untouched XP .iso without an external driver which is not part of the grub4dos package."

There are no answers AFAIK as it is not a problem.


i haven t said this. but if i am honest, my personal sentence atm is, that the grub4dos-devs don t care about user interests, becouse they have their own ideology, scope or whatever. the decision if this is a good or bad thing, must everyone make with himself. for me, this is a negative point about grub 4 dos. this is only my personal sentence based on how i interprete and understood the many things i read about this subject.

regards

livedude

p.s: why i can t edit older post from me? the option for it seems to be gone.

Edited by livedude, 25 March 2012 - 06:47 PM.


#6 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14758 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 25 March 2012 - 06:48 PM

Until you don't delve into the technical aspects I doubt you can fully understand the issue at hand.

What would be the reason for the grub4dos Authors :worship: to develop a suitable NT kernel driver, since such drivers ALREADY EXIST and work allright in conjunction with grub4dos? :dubbio:

I would understand if you had posted this kind of considerations before Firadisk and Winvblock were available, and in any case you missed a part of the story.

JFYI, one of the grub4dos developers did develop a suitable kernel driver to boot NT based systems:
http://www.disklessangel.com/en

The advantage of using firadisk is that it is not only a "RAMdisk" driver but also a "Filedisk" driver, i.e. you need NOT a huge amount of RAM to accomomdate the.iso.

BTW with the advent of later OS (Vista :ph34r: and 7 - and also the future 8) such a driver is not needed anymore in most cases (as it is already provided by the MS guys), and when needed there are even more "third party" solutions like IMDISK is for the Windows 7 install DVD.

And - again - the scope of grub4dos is to start (in your own words)

... that grub is able from the technical side, to start these untouched xp and others iso`s ....

and whatever happens after this start is NOT part of grub4dos scope (but, as seen there are other good programmers that provided the necessary tools).


:cheers:
Wonko

#7 livedude

livedude

    Member

  • Members
  • 83 posts
  •  
    Germany

Posted 25 March 2012 - 07:13 PM

Hi Wonko,

And - again - the scope of grub4dos is to start (in your own words)


but not to start everything... ;)

well, it seems we have different sentences and this is also completly ok.
so a democracy is working.
i acept your sentence but i don t share it (as far as i have understood the relevant aspects).
so, i think its already all relevant said about this grub-subject.

maybe you can help me with an other thing.
i don t completly understund this ramd disc syntax uses for loading ramdisks that an untouched xp iso can start.
so i can t try it.
my live-system as that: its an iso and inside this iso in Boot/IMG are the isos wich i wana start from the grub-menu.
therefore i use normaly commands like that:


title test
find --set-root --ignore-floppies /Boot/IMG/name of .iso
map /Boot/IMG/name of .iso (hd32)
map --hook
root (hd32)
chainloader /BOOTMGR

or


title test2
ls /Boot/IMG/Win7.iso || find --set-root /Boot/IMG/Win7.iso
map --heads=0 --sectors-per-track=0 /Boot/IMG/Win7.iso (0xff) || map --heads=0 --sectors-per-track=0 --mem /Boot/IMG/Win7.iso (0xff)
map --hook
chainloader (0xff)

and so on.

if i use now the syntax from this ramdisk-threads "(hd,0) then this isn t working.
again, my live-system is an iso with otheres iso`s inside this ios wich must be startet from grub startmenu.
maybe you can help me with this.

regards
livedude

Edited by livedude, 25 March 2012 - 07:21 PM.


#8 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14758 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 26 March 2012 - 08:44 AM

Well, you will need to go into "technical details".

A good start would be reading the grub4dos Guide:
http://reboot.pro/forum/66/
http://reboot.pro/5187/
http://diddy.boot-la...os/Grub4dos.htm

You do need to get the basics before anything else.

Basically:
find --set-root --ignore-floppies /Boot/IMG/name of .iso
tells grub4dos to scan all devices it can see to find in any of them " /Boot/IMG/name of .iso", first occurrence is found, the device is set as ROOT.
"0" is NOT a device. :w00t:
(hd0) is the WHOLE first disk.
(hd0,0) is the first partition on first disk.
(fd0) is the first floppy disk.
(cd) is normally the physical CD drive

As a rule of thumb never use (unless intentional) hardcoded devices and always use "find --set-root" instead.
Remember that FiLeNaMeS oN Cd/DvD aRe CaSe SeNsItIvE!

If you have further questions on grub4dos you should:
:cheers:
Wonko

#9 livedude

livedude

    Member

  • Members
  • 83 posts
  •  
    Germany

Posted 26 March 2012 - 06:01 PM

Hi Wonko,

thank you very much for this instructions. i added it to my guide with grub4dos booting instructions.
well, i have no problem with going into technical details where it is necesary to get things work.
the last days and long nights i spend with seaching for examples how grub4dos can start this and that.
your instructions are a good starting point, but what would help me more, woulb be a concrete example of starting a untouched xp.iso with such an ramdisk with my iso structure:

example:
win-xp.iso is in /boot/IMG/xp.iso
the ram disk is als in /Boot/IMG/ramdisk.img /viradisk/whatever.

for this i need an example that loads the ramdisk and start the xp.iso then.

if i have such an concrete example, it would save me much time and i can abstract the result, so that i can use also for other things.
thats the way i am learning and so i already learned much about this things,

so if you can give me a concrete example with my iso-structure, thats would save me a lots of time and i can learn much about it.
this would also help me faster to reach my goal, then to read a lots of basic, wich are fixedly intereseting but not helpfull for my concrete proplem.
if you can do this, very nice.
if not, also no proplem, becouse is only a please and no must do.

best regards
livedude


p.s.:
i have reflect what you have said about grub4dos and i think, i can now understund you a little bit better:
you and maybe the devs think: its only the job from grub4dos to start things. if they work after starting is not important. grub has finish its job, if things are startet.
well, me as typical enduser has a complete other viewpoint:; its not enugh to start things, they must also work after starting, if they do not, its useless.
i refer that in the hope that we can understund the othere-one better. your viewpoint, my viepoint (the enduser-viewpoint) ;)

Edited by livedude, 26 March 2012 - 06:04 PM.


#10 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14758 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 26 March 2012 - 06:30 PM

Hi Wonko,

thank you very much for this instructions. i added it to my guide with grub4dos booting instructions.
well, i have no problem with going into technical details where it is necesary to get things work.
the last days and long nights i spend with seaching for examples how grub4dos can start this and that.
your instructions are a good starting point, but what would help me more, woulb be a concrete example of starting a untouched xp.iso with such an ramdisk with my iso structure:

example:
win-xp.iso is in /boot/IMG/xp.iso
the ram disk is als in /Boot/IMG/ramdisk.img /viradisk/whatever.


for this i need an example that loads the ramdisk and start the xp.iso then.

if i have such an concrete example, it would save me much time and i can abstract the result, so that i can use also for other things.
thats the way i am learning and so i already learned much about this things,

so if you can give me a concrete example with my iso-structure, thats would save me a lots of time and i can learn much about it.
this would also help me faster to reach my goal, then to read a lots of basic, wich are fixedly intereseting but not helpfull for my concrete proplem.
if you can do this, very nice.
if not, also no proplem, becouse is only a please and no must do.

The issue is this. :(
There are two tested approaches (one that uses a Ramdisk and one that uses direct access), to which you have been already given a link:
http://www.msfn.org/...aded-iso-image/
http://www.msfn.org/...rom-a-iso-file/

You should decide WHICH one of the two you want to try, then follow the given instructions to the letter WITHOUT introducing ANY change of ANY kind.
Once you have succeeded in replicating EXACTLY the given steps, THEN, and ONLY then, you can try introducing changes (and this includes structure of the source device).
Of all the possible .iso images that you could choose to test your abilities and learn usage of grub4dos, you chose one of the most "tricky" ones, because you sum to the .iso booting problem the "quirks" of Windows install.

p.s.:
i have reflect what you have said about grub4dos and i think, i can now understund you a little bit better:
you and maybe the devs think: its only the job from grub4dos to start things. if they work after starting is not important. grub has finish its job, if things are startet.
well, me as typical enduser has a complete other viewpoint:; its not enugh to start things, they must also work after starting, if they do not, its useless.
i refer that in the hope that we can understund the othere-one better. your viewpoint, my viepoint (the enduser-viewpoint) ;)

Yes, but you see, your "user" viewpoint is perfectly "normal" and "respectable", it is perfectly understandable how the "final user" is interested to the result and not to the technical minutiae.
The problem is when you assume that:
  • someone *must* solve your "final user problem" (and for free)
  • that this *someone* are the grub4dos developers
  • that if *they* do not solve your problem they didn't because they don't care about you or there is some form of conspiracy against you having boot a NT based .iso
You (like anyone else using these tools) should be VERY grateful to them because they solved a part of your "final user problem", as well as you should be grateful to Sha0 (author of winvblock) and to Karyonix (author of firadisk) and to cdob (that put together the various pieces of the solution to your "final user problem) and also be grateful to another bunch of people that posted suggestions/ideas/refined the methods, wrote the English grub4dos guide, and help other people with their issues on the various boards, etc., etc. (remember that all of them do what they do for free and subtracting some of their time to their work or family to write tools or post advice in order to help other people solve problems and they do it because it's fun and they like to help other people).

:cheers:
Wonko

#11 livedude

livedude

    Member

  • Members
  • 83 posts
  •  
    Germany

Posted 26 March 2012 - 06:58 PM

HI Wonko,

thanks again for your help.

i have the impresion you don t have understood me correct:

Yes, but you see, your "user" viewpoint is perfectly "normal" and "respectable", it is perfectly understandable how the "final user" is interested to the result and not to the technical minutiae.


in case of getting things startet with grub4dos, i am of course interestet in the technical details wich are necesary for that.
i only said, that i am not interesting in the exact technical details, to make grub4dos able to start untouched xp.iso`s and other things, so that hey work. in this case, grub4dos needs an suitable driver or something, the exact tehcnical details, are not so important for me, becouse the thing is, that it is technicaly posible to do that. how exactly, is a question for the devs and not for me as enduser, becouse i don t have the intention and also not the knoweldge to do this.

it looks completly different, if the goal is, to give me a working syntax for starting things with grub4dos, that i can finish my project.
there i am of course very interestet in technical details becouse without them, i can t finish my job.
you see, these are two complete different things, at least for me.
so it is wrong to say that i am not interestet in technical details general at all.

and some word to be "gratefull".
i am very greatfeull to all that people, infesting their time, to give working solutions.
they do a very great job.
if you have had the impresion that i am not grateful, then this completly wrong!
i only said honest what i am thinking about the proplem we talked in the gebinning. not more and not less.

so, now i have work trying to get things running.
again, thank you very much for you help and if still present, drop that doubt that i am not grateful. its completly wrong.
i am very grateful.

best regards

Edited by livedude, 26 March 2012 - 07:02 PM.


#12 cdob

cdob

    Gold Member

  • Expert
  • 1438 posts

Posted 26 March 2012 - 07:43 PM

in case of getting things startet with grub4dos, i am of course interestet in the technical details wich are necesary for that.

You have to understand the basics:

grub4dos works at BIOS level.

Windows XP setup uses BIOS level at textmode too: mapped ISO image is available
Windows drivers are loaded and initialized at that stage.

Next at guimode:
mapped ISO image is not found at windows default drivers: BSOD 0x7b
If you add a proper windows driver, mapped ISO image is found: booting continues

This goes to all grub4dos mappings:
Mapped image has to support this too.

#13 livedude

livedude

    Member

  • Members
  • 83 posts
  •  
    Germany

Posted 26 March 2012 - 08:07 PM

Thank you cdob for the hints and explanation.
i try edit the giving example in the links for starting xp.with ramdisk, make usable for my project.
like i already said: its an iso with iso`s inside:
the path to the iso`s inside the iso are: /Boot/IMG/name of image to start.iso/.img
the createt iso with the isos inisde will be startet at virtualbox as bootbale cd/dvd-rom.
for this scenario i must somehow create a working start syntax for the xp iso:

for example:

title start untouched xp.iso for installation WindowsXP
find --set-root -- /Boot/IMG/xp.iso
and then path and command to ramdisk like winv/fira?
that is what i have to work out.
the only thing i need, is a working syntax for my example.
lets see, mabye i have luck:)

thx again for you help (also to Wonko)!

best regards
livedude

p.s: oh yes that grub4dos is case sensitive i found out very hard on my own.
path and evrything were correct but it was able to finding anything.
then the throught came: maybe it need case sensitive, but what for a sense makes it, that a bootmanager needs that? never mind, just try it.
so tried it with case sensetive and found out, that after long spendet time myself, it worked. i better don t asks the question wich came in my mind, for what such a programm needs case sensitive;)
its also not so important since i know now that grub (for what ever reasons) needs it and now my things are running:)

Edited by livedude, 26 March 2012 - 08:16 PM.


#14 cdob

cdob

    Gold Member

  • Expert
  • 1438 posts

Posted 26 March 2012 - 09:16 PM

for this scenario i must somehow create a working start syntax for the xp iso:


http://www.msfn.org/...post__p__991048

v06 major redesign
A sample menu.lst is included.



#15 livedude

livedude

    Member

  • Members
  • 83 posts
  •  
    Germany

Posted 27 March 2012 - 01:15 AM

Tank you cdob, but i don t have access to the needed files.
it seems you must register for that.
is there maybe an alternative source for getting v06 major redesign ?







best regards

livedude

#16 livedude

livedude

    Member

  • Members
  • 83 posts
  •  
    Germany

Posted 27 March 2012 - 04:00 PM

bevor you read, pleae allways keep in mind, that i am a typical enduser. i am no developer, i am no programmer, i am a enduser only.
endusers normaly only want use the things that the can finish their work/projects. they don t will become experts knowing all details of anything. they are lucky if the know enough to finish their work. from this viewpoint, i wrote my thoughts.

update:

after another spendet night with finding the correct syntax, that grub4dos start what i want (in this case a untouched sp.iso), i have a working solution.
with this configuration, you can start an untouched xp.iso, from your iso-compilation. maybe also from a usb-stick.
it needs at least 711mb ram;((, but ok, better then nothing.
maybe if i a spend many nights with working again, i find a solution wich needs not so much ram. for example: my createt win7-pe-system, works at a minimum ram of 256mb....



title test1
find --set-root /Boot/IMG/firadisk.img
map --mem /Boot/IMG/firadisk.img (fd0)
map --mem /Boot/IMG/Winxp.iso (hd32)
map --hook
root (hd32)
chainloader

may it help someone and avoid him to spend sooo many time (like me) before he finds what he is looking for.
well, if i am honest, i can t understund this acting. i only asked for one, only one, concrete example that i could finish my work.
i don t get one. i was again on my own...
if anyone has a concrete problem in an area i have knowledge, then i try to help him.
i don t say, if he has for example a windows-problem: "here is a link to the basic from windows. you can see how it works and learn everything about it and if you have much luck, then you are able at the end to solve you problem. but propaply you are not".

no thats not the way, i am handle this things. i ask: "in wich situation/when the problem ocures/what you wana do"?
and then i try to give a working solution.
but i remember this idology: you have to learn bevor you can use it.
i was sure that i know it and that i have heard it before.
oh yes, it comes from linux!
let us look if people acept it and where linux is now on the consumerdesktop:
http://marketshare.h...re.aspx?qprid=8

oh, its by 1,07% on the consumer desktop and windows dominates the rest.
why weal? is this an coninsident? i think its not. this idelogy that you must learn everything and all, bevore you can use anything has failed and the majority of the people are against it. thats the reason becouse linux gets no step on the desktop.
but enough from that.

i am glad that i have a working example now and i hope this concrete! example
helps others with the same problem, too.

i don t share some opionions here, anyway, thanks a lot for the help!

best regards

livedude

Edited by livedude, 27 March 2012 - 04:16 PM.


#17 cdob

cdob

    Gold Member

  • Expert
  • 1438 posts

Posted 27 March 2012 - 05:38 PM

i only asked for one, only one, concrete example that i could finish my work.

What about reading previously given links?
Read first post http://www.msfn.org/...rom-a-iso-file/

Or http://www.msfn.org/...post__p__958096
This refers to firadisk author example:http://reboot.pro/8804/

Or http://www.msfn.org/...post__p__988072

#18 livedude

livedude

    Member

  • Members
  • 83 posts
  •  
    Germany

Posted 27 March 2012 - 06:03 PM

for the first link it seems you need this "Inst/XP_RAM.ISO" and other files, wich seems part of the v06 major redesign, for i don t have access .
the same for the secound link.

with the examples from the third link, i could not work correctly,
becouse it was not usable for my projekt.
exactly to avoid this scenary, i asked for a concrete example for my projekt
i postet its structure: an iso with iso`s inside, start examples and i gave the path.
i think that was enough information for giving me a quick concrete example for my project.
but this wasn t the case. so i found again everything out of my own.
but its no problem, becouse there is no must, in giving asking people concrete examples that they can faster finish their job.
but i must not like it. thats part of my freedom.
i am glad that i am now a little step further with my work.
thx again for everything.

best regards

live dude

Edited by livedude, 27 March 2012 - 06:14 PM.


#19 cdob

cdob

    Gold Member

  • Expert
  • 1438 posts

Posted 27 March 2012 - 07:15 PM

exactly to avoid this scenary, i asked for a concrete example for my projekt

Well, this assumes a user has a example relating your project.
However a ISO file inside a CD/DVD is seldom used.
Most likely no user has a concrete example.

i postet its structure: an iso with iso`s inside, start examples and i gave the path.

Actually different names.,

find --set-root -- /Boot/IMG/xp.iso
map --mem /Boot/IMG/Winxp.iso (hd32)

It's difficult to guess the concrete name.

i am glad that i am now a little step further with my work.

Did you made a full installation so far?


Based on http://reboot.pro/13967/

Not tested, may work or fail
title 1 Start Windows XP setup

map --mem (md)0x800+4 (99)

map /Boot/IMG/firadisk.img (fd0)

map /Boot/IMG/Winxp.iso (0xff)

map --hook

write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/Boot/IMG/Winxp.iso;floppy,vmem=find:/Boot/IMG/firadisk.img;\n\0

chainloader (0xff)



title 2 Continue Windows XP setup

map --mem (md)0x800+4 (99)

map --hook

write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/Boot/IMG/Winxp.iso;\n\0

chainloader (hd0)+1


#20 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14758 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 27 March 2012 - 07:24 PM

Just for the record, registering on MSFN is perfectly free, so, just like you registered here you can register there.

:cheers:
Wonko

#21 livedude

livedude

    Member

  • Members
  • 83 posts
  •  
    Germany

Posted 27 March 2012 - 07:55 PM

also for the record: maybe one don t want to register in another board (and another, another, another), only that he can download a few very small files;)

best regards

livedude

#22 livedude

livedude

    Member

  • Members
  • 83 posts
  •  
    Germany

Posted 27 March 2012 - 11:42 PM

update:

it seems i arrvied the next border. i can t attach iso-files bigger then 2gb´s to my compilation. propably a problem with mkisofs. so it seems that i must edit the iso-creation script, and add the correct lines, that mkisofs takes this bigger files?!
till now, i don t found a solution.
this boarder is tricky, becouse if i can t build live-systems only with a max amount of 2gb, then more as the half space of an standard dvd keeps un-used. from an double-layer dvd i will not speak at all...
if anyone knows an, if its possibe, easy way, to fix this issue, please let me know.

best regards

live dude

#23 cdob

cdob

    Gold Member

  • Expert
  • 1438 posts

Posted 28 March 2012 - 04:18 AM

Mkisofs adds files up to 8 TB since several years.
Use a current version and -iso-level 3 or up.

#24 livedude

livedude

    Member

  • Members
  • 83 posts
  •  
    Germany

Posted 28 March 2012 - 04:42 AM

Thank you, but i fear that it ist not that easy. i use the create iso.cript for building my iso. in /Boot/IMG/ my iso.s are going. if i put the win7-iso in it, wich is about 2,3gb big (32bit version for testing), then it ignores the content of IMG (the win7.iso) or breaks at bulding.
the create iso script uses mkisofs and i read on some places, that mkisofs should have problems with files bigger then 2gb`s. .
i already used a curent version of mkisofs: the latest build and stable.
i found out, that the create iso script, uses a mkisofs version from this path /projects/tools/win7pe_se/mkisofs.exe. so of course i copied the current version of mkisofs to that folder.
it isn t working and the new version of mksofs also needed two addentional dll`s cygwin and a other dll. so i copied of course this two dll`s, two.
then i looked into the script finding out wich commands it uses for bulding the iso. i found three lines wich i hope that this the right ones.
example of such a line:

"ShellExecute,%Show_mkiso%,#$q%Tools%mkisofs.exe#$q,"-iso-level 4#$s-force-uppercase -volid #$q%Volume_Name%#$q -b #$q%BootSect%#$q -no-emul-boot -boot-load-size 8 -hide boot.catalog#$s-duplicates-once -o #$q%ISOfileVar%#$q #$q%targetdir%#$q""

of course i also found out with google, that mkiosfs need this iso-level 3 commands. of couse i changed the iso-level 4 from the script, to iso-level 3. without luck.
i think more i can t do. have no posibility`s to correct the issue. never before i needed mkisofs for something, first since i use winbuilder. i know as good as nothing about it. i hope its possible to fix this issue somehow that i can finish my project.

best regards

live dude

Edited by livedude, 28 March 2012 - 04:47 AM.


#25 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14758 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 28 March 2012 - 09:12 AM

of course i also found out with google, that mkiosfs need this iso-level 3 commands. of couse i changed the iso-level 4 from the script, to iso-level 3. without luck.

Strangely enough iso-level 4 has "more capabilities" that iso-level 3, and there is NO reason to change it if not for compatibility with older bootmanagers/filesystem drivers.

I do suspect that somehow you have not a great familiarity with the English language, this:

Mkisofs adds files up to 8 TB since several years.
Use a current version and -iso-level 3 or up.

means:
DO NOT use iso-level 1 or 2.
DO USE iso-level 3 or 4.


also for the record: maybe one don t want to register in another board (and another, another, another), only that he can download a few very small files;)

Sure :), this is freedom.
You were given a number of suggestions, you are perfectly free NOT to follow them or to introduce changes to them.

Only, you should understand how this freely made decisions make your progresses more slow and possibly even non-existing :ph34r:.

There are very few things that make me so upset :frusty: as to decide stopping attempting to assist a member of the board :(, and these are those listed in the "common sense advice":

Maybe you missed them :unsure:, though it's strange since you posted here :dubbio::
http://reboot.pro/forum/33/
and they are exactly there as "sticky":
http://reboot.pro/2420/

Have fun with your projects, that's the only important thing. :)

:cheers:
Wonko




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users