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 in a single pos
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:
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 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.
Edited by livedude, 25 March 2012 - 05:06 PM.