Jump to content











Photo
- - - - -

Project authors - read this!


  • Please log in to reply
11 replies to this topic

#1 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12688 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 28 September 2009 - 05:13 PM

A lot of (even experienced users') trouble reports are based on the fact that they positioned their %BaseDir% into a non-suited directory.

Urgent suggestion to project authors:

In script.project [process] check whether %BaseDir% has an 'allowed' value

E.g. in Vista or Win7 based projects it brings troubles, if %BaseDir% is under the local host's profiles directory.

Sample:

StrFormat,POS,%BaseDir%,%UserProfile%,%pos%

 If,%pos%,EQUAL,1,Halt,"You Fool!"
And maybe:

Even if WinBuilder handles spaces in path names actually well:
If the author is convinced that spaces in the path are not allowed, he should do the check here, too.

It is frustrating for new users, when after building a project (taking a long time)
  • The PE does not start or brings errors
  • They ask in the forum
  • And get the answer: Wrong %BaseDir%
The 'Wrong %BaseDir%' should be given by the project on start!

#2 TheHive

TheHive

    Platinum Member

  • .script developer
  • 4137 posts

Posted 29 September 2009 - 11:17 PM

That would save alot of time.

#3 paraglider

paraglider

    Gold Member

  • .script developer
  • 1716 posts
  • Location:NC,USA
  •  
    United States

Posted 30 September 2009 - 12:12 PM

Winbuilder could also check if its running in a directory that may cause problems and give a warning popup.

#4 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12688 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 30 September 2009 - 02:27 PM

WinBuilder generally can work with every valid directory, even on network drives. Spaces in the name do not matter.

Some scripts, or better said apps started by them like ImageX, have difficulties.

Therefore the projects with scripts having some directory restrictions, must check.

e.g. nativeEx has no restrictions. And it is wrong when WinBuilder pops:
"You cannot work under Documents and Settings"

Peter

#5 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 30 September 2009 - 03:00 PM

WinBuilder generally can work with every valid directory, even on network drives. Spaces in the name do not matter.

Some scripts, or better said apps started by them like ImageX, have difficulties.

Therefore the projects with scripts having some directory restrictions, must check.

e.g. nativeEx has no restrictions. And it is wrong when WinBuilder pops:
"You cannot work under Documents and Settings"

Peter


Which sums up nicely to, in "Dinosaur's language" :D:
  • DON'T TRUST ANYONE: PEOPLE AND PROGRAMS EITHER LIE OR ARE WRONG
  • IGNORE ANYTHING YOU ARE USED TO BY WINDOWS, GOOD OL' DOS NAMES ALWAYS WORK, IGNORE ALSO THE AUTOMATED CHECKS AND WARNINGS IF ANY
  • DON'T USE PATHS WITH SPACES
  • USE A SIMPLE, NICE, SHORT PATH, LIKE C:\WB078

Since I am notoriously aggressive when it comes to this non-issues made into issues by the lack of frankness, or by the programmer's pride, I would operate the reverse way.

A CLEAR WARNING:

Though the great Authors of Winbuilder have made it compatible with any possible PATH, a number of third party apps or .scripts made by a few not "up to the standard" contributing members may NOT work with paths with spaces in them or situated in particular places of the filesystem, Winbuilder has been intentionally restricted to run with a %basedir% that can ONLY be:
wb<a maximum of 6 alphanumeric characters>\
placed in the ROOT of a drive.
If you want to run it from ANYWHERE else, write your own builder. :whistling:


:D

jaclaz

#6 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12688 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 30 September 2009 - 03:52 PM

I give up!

Appearently I'm the only one of 28.000 users where WinBuilder works well with a space in the path of %BaseDir%

And the 'No Space' opinion is so hardcoded in the mind of some users that

Even if WinBuilder handles spaces in path names actually well

WinBuilder generally can work with every valid directory, even on network drives. Spaces in the name do not matter.

in two different post here, is interpreted as

may NOT work with paths with spaces


It is pure mathematical logic:

Do you agree to:
  • A bear is an animal
  • A bear cannot fly
  • Therefore animals cannot fly
Here we have
  • Under WinBuilder ImageX mounted WIMs bring troubles when they are mounted under the profile directory
  • The profile directory usually has spaces in the path like "Documents and Settings"
  • Therefore a WinBuilder started Imagex cannot handle spaces in the path
  • Therefore WinBuilder cannot handle spaces in the path
As said: I give up. No more trials to stop the rumor.

Peter :whistling:

BTW: @jaclaz: If you omit

with paths with spaces in them or

and

Winbuilder has been intentionally restricted to run with a %basedir% that can ONLY be:
wb<a maximum of 6 alphanumeric characters>\
placed in the ROOT of a drive.

your suggestion could be acceptable.

#7 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 30 September 2009 - 04:12 PM

I am not saying that Winbuilder actually has this limit, actually the opposite, I am saying that Winbuilder has NOT this limit.

I am saying that third party apps and/or not fully "kosher" .scripts may have this problem.

THUS, I am trying to do a paradigm shift, instead of saying that something (WHATEVER it is) may go wrong, I say:

  • If you build a directory structure where winbuilder is in a folder DIRECTLY under ROOT and is named wb<max 6 alphanumeric characters>, it will SURELY work.

And, additionally:
  • More generally, anything, if you use on your filesystem ALL PATHS without spaces in them it will SURELY work.
  • Even better, if you are able to also use ALL 8.3 compatible filenames, it will SURELY work.

:whistling:

jaclaz

#8 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12688 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 30 September 2009 - 04:21 PM

:whistling:

I only wanted to prohibit that the opinion comes up:

WinBuilder Paths MUST be ...

Peter :D

#9 paraglider

paraglider

    Gold Member

  • .script developer
  • 1716 posts
  • Location:NC,USA
  •  
    United States

Posted 30 September 2009 - 07:27 PM

All I suggested was a warning. Just like you get on a packet of cigarettes.

#10 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 01 October 2009 - 07:54 AM

Something like:

WARNING: Winbuilder may be addictive.
You may soon be hypnotized by the blue progression bar.
Be smart, don't overdo it, put it in C:\WB07x directory.

:whistling:

:D

jaclaz

#11 Nuno Brito

Nuno Brito

    Platinum Member

  • Team Reboot
  • 10447 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 01 October 2009 - 08:57 AM

All I suggested was a warning. Just like you get on a packet of cigarettes.


Nice idea, has anyone mentioned this to either YahooUK or Joshua? ;)

WARNING: Winbuilder may be addictive.
You may soon be hypnotized by the blue progression bar.
Be smart, don't overdo it, put it in C:\WB07x directory.


Continuing the restrictions at this rate, we'll soon come to a point where wb won't be allowed inside closed spaces and people wanting to use it will have to move onto the street or wb booting points to keep the air clean.

:whistling:

#12 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 01 October 2009 - 11:42 AM

Continuing the restrictions at this rate, we'll soon come to a point where wb won't be allowed inside closed spaces and people wanting to use it will have to move onto the street or wb booting points to keep the air clean.


Actually you should issue a Licence for it (not a Licence in the sense of an EULA, rather a Licence like a Driveing License).
Such a License or Permit should be obtained by the Author(s) after a quick test of Winbuilder, through answering an online test, one of those choose one or more of the possible answers.

Q1: Do you think you are smarter than Winbuilder?
A1a: Yes.
A1b: No.
A1c: Somewhat.

Q2: Do you have enough time to ignore the warnings, fail to read any possible messages, omit reading the docs and get stuck in an endless loop?
A2a: Yes, I do actually like seeing that blue progression bar across my screen, they are so round and repetitive, I like predictable things.
A2b: No, I have read all the docs available and followed exactly the tutorial at hxxp://www.boot-land.net/forums/index.php?showtopic=xxxx and it doesn't work as well.
A2c: I haven't read anything, and won't in the future, the app worked allright and this whole idea of a License for using it is pure nonsense.

Points:
A1a - 0 points, the applicant thinks he knows more than he actualy does
A1b - 0 points, the applicant is a liar
A1c - 2 points
A2a - 0 points
A2b - 0 points, the applicant is a liar
A2c - 2 points

One would need at least 4 points to pass the test.....;) ;)

:whistling:

jaclaz




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users