I should perhaps clarify that this post is more about the winbuilder projects than winbuilder itself.
The comments in this post are entirely my own opinion. Please bear in mind that I am speaking from my own perspective as a winbuilder noobie.
I read with great interest this thread by MedEvil - Little Rant.
For the record, my intention here is not to upet anyone. I just want to...
As an outsider I can honestly say that the Winbuilder projects would (IMO) benefit far more people if some of the points raised in the Little Rant thread were addressed. I'm not going to mention any particular projects - I have attempted to use several.
Nuno Brito stated (here) -
Nuno really hits the nail on the head. Excuse the profanity however people (myself included) can be lazy b@stards. Time is precious to me right now and the Winbuilder projects I have experimented with are not user friendly enough for my needs. I feel that they have perhaps become elite or require too much specialist knowledge to get them working. Something with such a steep learning curve is going to put off a lot of people - some of whom may never return.
After successfully building a working XP based project (after several attempts that didn't work) I made a backup of the resulting ISO and have since scripted various batch files that allow me to mount and edit it. This took hours, but for me was preferable to having to use Winbuilder again.
This is not an attack on winbuilder but is a reflection on how complicated projects can become. I personally think that some projects try to achieve too much in terms of covering all bases. This just adds to the amount of user defined options and further moves away from the winbuilder process being intuitive or simple.
Please bear in mind also that I'm well experienced with building and using Windows PE and have an above average understanding of Windows PE. If I'm struggling to get things working with my experience than how do you think newcomers will feel?
Regards,
Misty
p.s. Let the flaming begin
The comments in this post are entirely my own opinion. Please bear in mind that I am speaking from my own perspective as a winbuilder noobie.
I read with great interest this thread by MedEvil - Little Rant.
MedEvil, on 16 May 2010 - 01:42 PM, said:
When we started out or at least when i joined, the goal was to build a better PE and have our projects be easier to use.
I think we acomplished the first .....But with the second we failed miserably.
I think we acomplished the first .....But with the second we failed miserably.
For the record, my intention here is not to upet anyone. I just want to...
Quote
Participate: You don't need to be an expert, write your opinions and learn
As an outsider I can honestly say that the Winbuilder projects would (IMO) benefit far more people if some of the points raised in the Little Rant thread were addressed. I'm not going to mention any particular projects - I have attempted to use several.
Nuno Brito stated (here) -
Quote
If Hiren is popular, is because people nowadays still don't see the current building processes available as intuitive or simple that can be done in two or three clicks without fuss. This means that our own works need to be made simpler, and not just "elite".
Nuno really hits the nail on the head. Excuse the profanity however people (myself included) can be lazy b@stards. Time is precious to me right now and the Winbuilder projects I have experimented with are not user friendly enough for my needs. I feel that they have perhaps become elite or require too much specialist knowledge to get them working. Something with such a steep learning curve is going to put off a lot of people - some of whom may never return.
After successfully building a working XP based project (after several attempts that didn't work) I made a backup of the resulting ISO and have since scripted various batch files that allow me to mount and edit it. This took hours, but for me was preferable to having to use Winbuilder again.
This is not an attack on winbuilder but is a reflection on how complicated projects can become. I personally think that some projects try to achieve too much in terms of covering all bases. This just adds to the amount of user defined options and further moves away from the winbuilder process being intuitive or simple.
Please bear in mind also that I'm well experienced with building and using Windows PE and have an above average understanding of Windows PE. If I'm struggling to get things working with my experience than how do you think newcomers will feel?
Regards,
Misty
p.s. Let the flaming begin