45 replies to this topic

[MedEvil]

Today, while helping to set up a new computer and transferring data, i've got curious, how fast an up to date gaming PC would run NaughtyPE.
It did boot, from CD (ramboot), as fast as Win7 from HDD. Full hardware detection didn't took only seconds, but actually a second!

Problem was, that neighter mouse nor keyboard worked, yet the hotplug symbol could be seen in the systemtray.

Did this happen to anyone else, or do we might even know, why it didn't work?

[was_jaclaz]

Problem was, that neighter mouse nor keyboard worked, yet the hotplug symbol could be seen in the systemtray.

USB or PS/2?

jaclaz

[MedEvil]

As the title says, USB mouse and keyboard.

It's the first time ever i have used NPE with a USB Keyboard, but USB mice used to work fine.
Also i had never anyone complain about USB mouse or keyboard not working. So i'm a bit stumped.

[was_jaclaz]

I would try something like this:
http://www.boot-land...?showtopic=3857

AFAICR the problem is just the keyboard, that may influence mouse also.

In other words:

• PS/2 Mouse+PS/2 Keyboard ALWAYS work
• USB Mouse+PS/2 Keyboard USUALLY work
• USB Mouse+USB Keyboard may not work (just the keyboard or both keyboard and mouse)

Sometimes "switching" ports work, DELL's (once again) are reknown troublemakers, and old report:
http://www.911cd.net...?showtopic=5898

jaclaz

[Lancelot]

@jacklaz

just to update info:
mentioned script at first link of your post replaced from livexp and nativeex_barabone server by "Removable Devices Combo" script written by fxscrpt.
service note attached to the link.

[was_jaclaz]

@jacklaz

just to update info:
mentioned script at first link of your post replaced from livexp and nativeex_barabone server by "Removable Devices Combo" script written by fxscrpt.
service note attached to the link.

Good , so presuming, for the only reason of arguing a bit , that someone wants to have a look for whatever reason to the "old" attempt, it is not anymore available.

Since it has not been archived "casually" by The Wayback Machine, that piece of info is lost forever, or it is available, like:

It was on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying "Beware of The Leopard".

There are REASONS why I mentioned that .script:
http://www.boot-land...?...=3866&st=70
http://www.boot-land...?...=3866&st=72

Is it "the same .script" but updated?
Or is it a totally new approach?

One of my usual "philosophical" questions: How come we don't seem able to mantain things with a minimun of "order"?
A new .script replaces and old one, we have tens of posts on the board referring to the old one, the old one gets lost forever, effectively:

• subtracting knowledge from the Community
• making difficult for any "normal" human being to understand what is happening, where to find things, etc. etc.
• vanishing the utility of a thread or of single posts that contributed to better understand how things work

And since I am in one of my "grumpy" days , and to continue the tradition of going off-topic, can someone explain to me WHAT the heck of month is:
http://livexp.boot-l...net/updates.ini

;This file is automatically generated by psc program genUpdates version 3.4.0
;Date: 2009-Ara-03 11:18:17
;Command Line: genUpdates LiveXP Tools /TLiveXP

is "Ara"?

Are we using a new "Winbuilder Calendar"?

(Yes, we already adopted latin mediterranean timing , but a brand new calendar? )



jaclaz

[Lancelot]

Good , so presuming, for the only reason of arguing a bit

First of all, this is not a very new info, script added to project (and old ones removed) at 2009-09-13 . I remember a topic where I also inform Peter but could not find now (maybe my memory tricks me). Since you are "The Finder" and a Great Helper, I wanted to keep you up to date

Some interface pictures may help my bad english when trying to explain,

old hotplug script:

current Removable Devices Combo:

Or is it a totally new approach?

I select "B )" , new approach

Story is:
we had keyboard and usb mass storage scripts seperately before, and for a short while we had Ieee1394 script and '"safely remove devices" icon' option somewhere...

fxscrpt thought it is hard to maintain all these scripts & option seperately since they contain shared entries. So fxscrpt united all these options into single script.

As a result, nothing lost.

Script available on LiveXP at driver section and icon of interface is a union of old scripts/option to serve graphical memory of end users. Also description would help to good google searchers to find the new script.
So far none of LiveXP users posted that they lost the old script since it is very easy to find .

And since I am in one of my "grumpy" days , and to continue the tradition of going off-topic, can someone explain to me WHAT the heck of month is:
http://livexp.boot-l...net/updates.ini

is "Ara"?

Are we using a new "Winbuilder Calendar"?

I did not notice that before, I will report to psc now.
I use genupdates to generate updates.ini, in Turkish December=Aralık
Not my fault, ....

[was_jaclaz]

I use genupdates to generate updates.ini, in Turkish December=Aralık
Not my fault, ....

Yes, I know:
http://tr.wikipedia.org/wiki/Aralık

though I thought at first that we adopted months with the names of bird:
http://tr.wikipedia.org/wiki/Ara

In this was the case I would like to propose for "December" "mocking-bird" :
http://en.wikipedia....iki/Mockingbird
abbreviated as "mock" :
http://www.urbandict...e.php?term=mock





jaclaz

[Lancelot]

Yes, I know:
http://tr.wikipedia.org/wiki/Aralık

Yes, I know you know

abbreviated as "mock" :

[MedEvil]

I would try something like this:
http://www.boot-land...?showtopic=3857

That script is only to enable hotplug for USB keyboard and mouse.
With other words the driver installation was moved from txtsetup.sif to pnp. (to plug them in after bootup)
Since keyboard and mouse were pluged in before bootup.
This can't be the reason. But will try it anyway.

PS: Named script is still available on the NaughtyPE server. Do you like more static projects, now better?

[MedEvil]

Good , so presuming, for the only reason of arguing a bit , that someone wants to have a look for whatever reason to the "old" attempt, it is not anymore available.

It's still available at the NaughtyPE server. Version 2 that is.

One of my usual "philosophical" questions: How come we don't seem able to mantain things with a minimun of "order"?
A new .script replaces and old one, we have tens of posts on the board referring to the old one, the old one gets lost forever, effectively:

• subtracting knowledge from the Community
• making difficult for any "normal" human being to understand what is happening, where to find things, etc. etc.
• vanishing the utility of a thread or of single posts that contributed to better understand how things work

As usual i'm pro order, but there is just no way to store things in different locations and yet keep them in sync.
Eighter the scripts get stored in the threads, as we did when things started out, or we store them in some other place and break links from time to time.

In this special case, i'm with Lancelot. Not keeping old junk around, once it has been superseded by a better replacement, does not take away from the community, but helps make things more clear.
In the real world this is called cleaning up!

[was_jaclaz]

In this special case, i'm with Lancelot. Not keeping old junk around, once it has been superseded by a better replacement, does not take away from the community, but helps make things more clear.
In the real world this is called cleaning up!

Sure , I am all for the "cleaning", I am against the "clean and throw away", i.e. I'm for "clean and keep 'em in the basement, you never know when they will come useful again" AND "if you are gonna clean, clean thoroughfully", i.e. don't leave a number of references scattered around, half working, half not.

I don't think we have any size (not bandwith, mind you) problem on the liveXP server, why don't we have a "history" folder, we do not need anything sophisticated, look at the simplicity of the grub4dos "history" folder, why can't we have the "old" version zipped and with the date in the filename?
http://nufans.net/grub4dos/
http://nufans.net/grub4dos/history/

Why doesn't people (and this is directed ALSO as a suggestion to our Chinese friends of the grub4dos team) have a .log for changes where something more than a cryptic oneliner is written?

BTW even a one liner is MUCH better that no log at all , don't you think that threads like this one:
http://www.boot-land...?showtopic=7972
are a symptom of not-so-organized cleaning up?

Back to original topic, I guess that by re-plugging the devices after boot and using the USB PnP features something may change.




jaclaz

[Lancelot]

BTW even a one liner is MUCH better that no log at all , don't you think that threads like this one:
http://www.boot-land...?showtopic=7972
are a symptom of not-so-organized cleaning up?

not a good example , the specific script I guess removed accidentally before the log mechanism we have for a year (wow a year passed )

I don't think we have any size (not bandwith, mind you) problem on the liveXP server, why don't we have a "history" folder, we do not need anything sophisticated, look at the simplicity of the grub4dos "history" folder, why can't we have the "old" version zipped and with the date in the filename?

we have !! (and i guess you already know )
Archives publised when there is "The Vital Change" which is winbuilder version
LiveXP (074 archived) here http://winbuilder.ne...load.php?view.8
LiveXP (076 archived) here http://winbuilder.ne...oad.php?view.43
LiveXP (current) as you know here http://winbuilder.ne...oad.php?view.35

Also we have a set of archive similar to grub4dos, but not published in order not to mix minds. (versions between published archives)

Why doesn't people (and this is directed ALSO as a suggestion to our Chinese friends of the grub4dos team) have a .log for changes where something more than a cryptic oneliner is written?

we have !! (and i still gues you already know)
for server related script updates we have a log
http://livexp.boot-l...hangelog.script
and we also have a button on main screen of LiveXP to read that log
"View LiveXP ChangeLog" button: http://i487.photobuc...XP_Updatewb.png

Also for scripts, history notes taken, as an example check history info at following scripts
http://livexp.boot-l.../BootSDI.script
http://livexp.boot-l...Explorer.Script


I do not think a man who does not miss lines inside updates.ini can miss this infos
We have a phrase "My sister listen to me, My bride you understand, situation (We assume this action made by the mother of the son :>)"

[was_jaclaz]

I do not think a man who does not miss lines inside updates.ini can miss this infos

Re-read statement, please, bolded part for your convenience :

A new .script replaces and old one, we have tens of posts on the board referring to the old one, the old one gets lost forever, effectively:

• subtracting knowledge from the Community
• making difficult for any "normal" human being to understand what is happening, where to find things, etc. etc.
• vanishing the utility of a thread or of single posts that contributed to better understand how things work

My state of both having the brain of abby something:
http://en.wikiquote....ng_Frankenstein
and Vulcanian heritage excludes me from the number of those suffering from the problem.



jaclaz

[Lancelot]

jaclaz

I can not understand !!
nothing missing, If one wants an old copy of a script that is not used on LiveXP anymore than one can take it from the old available archive !!
ALL alive projects are quite active with the scripts they contain, project servers are not responsible to contain all scripts all the time. This is valid for all projects. Besides you may ask Galapo to provide the old script in his page if this is what you want.

As a "normal" human being I still do not fully understand things you write about the hd/mbr etc. stuff, the reason is me not working on it harder and not being a Vulcanian. Same is valid for the current log mechanisms of LiveXP, If a none vulcanian, "normal" human being wants to understand the log, (s)he should spend some time to understand. LiveXP frequent users (assuming they are normal human beings ) use log and history infos successfully on many cases to solve issues and check the progress.
We have log, we have history notes, we have button, we have a united script which includes same behaviour of previous, but we can not have jacklaz satisfaction

Enough boxing for today, as usual I loose
No body can beat The Italian Stallion

[MedEvil]

Back to original topic, I guess that by re-plugging the devices after boot and using the USB PnP features something may change.

jaclaz, i don't know if you understood right, it's one or the other, never both.
Thus far i used the non pnp variant.

Will test the pnp variant on saturday on the computer, not much else i can do.

[was_jaclaz]

jaclaz, i don't know if you understood right, it's one or the other, never both.

I am not sure either.

From what I understand, when a NT based system, including PE's, boots, it "scans" USB bus and (hopefully) loads drivers for peripherals it finds attached to it.
What it is NOT clear (to me at least) is how "strange" settings in the BIOS affect this, and my guess is that there are as many answers as many BIOS are there.
If you insert a new peripheral to the USB bus once the OS has booted a notification of some kind is sent to the system when the device is plugged (Plug n' Play) and the OS loads the appropriate driver for that device.
I presume that the first kind of scan can be affected, besides by the said BIOS settings, by some kind of timing problem, whilst the second (when PnP is working) should be "clean".
As well there are reports of different USB ports (meaning different sets of USB ports, i.e. groups of USB ports connected to different internal USB buses) behaving differently, hence the idea of trying moving devices around, as just llike attempting hot-plugging, it costs nothing to try.

@Lancelot
So, in order to peek inside a stoopid text file (please read as .script ) around 7 Kb in size I supposedly should download 166,3 Mb worth of files :
http://winbuilder.ne...oad.php?view.43
very comfortable and I would say convenient, expecially if you are on dial-up or on a wireless connection (yes, one of those for which you pay a dear price for each Mb downloaded).
We have already our friends at MS and the good Linux guys that think along these lines, so you are probably right (not meaning that you are actually "right", which in an actual confrontation with me is very, very improbable , "right" in the sense of "going with mainstream" ), myself remaining the last dinosaur that would like to get what he actually needs at the moment, without having to download "packages" of tens or hundreds of Mb he doesn't need/want.
Only yesterday, and this was part of the reasons why I was grumpier than usual, I downloaded a whopping 237 Mb on a sloppy wireless connection, around three hours wait, besides the actual cost, to find a simple 205 Kb doc I needed to review, of which only 3 (three) lines were the actual thing I needed.
This is in my view a way to "hide" things and favour the increase of total entropy.



jaclaz

[Galapo]

@jaclaz
The script in question may be obtained, as always, either via download of compressed image from winbuilder.net (preferrable option only if complete package is desirable), or the script itself from the livexp server: http://livexp.boot-l...cesCombo.script.

Regards,
Galapo.

[Lancelot]

jaclaz, There is a dilemma and an issue,
providing old archives with winbuilder servers
example:
http://livexp.boot-l...4-Archived_OLD/
http://livexp.boot-l...6-Archived_OLD/
probably fits some parts of your request
BUT
this will also cause google searchers find different livexp servers for a lot of common files (we would not like to mix minds)
ALSO
Even between packed 074-076, there might be a script added to 074 on an early period an same script could be removed (or replaced) by another and than 076 published. As a result opening new server do not fix the request of yours. (Even I personally do not have all versions of the scripts hehe)
REMINDING
I remember only 2 requests of older scripts in last year. 1 is for a bug chase which found later. 1 is asking for the last version of a script that is 076 compatible.

I feel it is not right to open new wb servers for archived builds, final decision is up to boss (Galapo).

ps: Is there any way to download a single file inside the zip archive on server. My memory hardly remember something about that but i am not sure.

I guess the "best" possible solution maybe at server side (if possible) so when we upload, server automatically renames the files that exists.! (Since we update scripts very frequently it would be very hard (&annoying&boring) to make this action manually each time for each script)
So when a user browse server he would get
UltraISO.script
UltraISO_200911041619.scriptOld
UltraISO_200911141123.scriptOld
UltraISO_200911260937.scriptOld

I guess this is what you want. Maybe better to ask Nuno.

[MedEvil]

As well there are reports of different USB ports (meaning different sets of USB ports, i.e. groups of USB ports connected to different internal USB buses) behaving differently, hence the idea of trying moving devices around, as just llike attempting hot-plugging, it costs nothing to try.

Never heared of that one. Good to know.

About the detection.
In a PE it is eighter done by the textbased part (setupldr+ntdetect+txtsetup.sif) or by the gui part (Hwpnp+ inf files)
Since i used the keyboard to access the BIOS, i'm sure that the BIOS settings are not to blame here.

Only yesterday, and this was part of the reasons why I was grumpier than usual, I downloaded a whopping 237 Mb on a sloppy wireless connection, around three hours wait, besides the actual cost, to find a simple 205 Kb doc I needed to review, of which only 3 (three) lines were the actual thing I needed.
This is in my view a way to "hide" things and favour the increase of total entropy.

There are a few download managers around, which can download only specific files from archives.
If you're often stuck behind slow lines, i would suggest getting one.
Or go to a place with a fast line and come back with the file later. 3 hours are more than enough to save time this way.

[MedEvil]

I guess the "best" possible solution maybe at server side (if possible) so when we upload, server automatically renames the files that exists.! (Since we update scripts very frequently it would be very hard (&annoying&boring) to make this action manually each time for each script)
So when a user browse server he would get
UltraISO.script
UltraISO_200911041619.scriptOld
UltraISO_200911141123.scriptOld
UltraISO_200911260937.scriptOld

I guess this is what you want. Maybe better to ask Nuno.

This may be what our web-archivist wants, but i seriously doubt that anyone else wants this.

This is like throwing away the preconfigured projects and offering an endless pile of scripts instead, from which people would need to figure out by themselfs what fits together and how and what not.

[was_jaclaz]

There are a few download managers around, which can download only specific files from archives.
If you're often stuck behind slow lines, i would suggest getting one.
Or go to a place with a fast line and come back with the file later. 3 hours are more than enough to save time this way.

Sure , I can even get an airplane get wherever the server is physically located, break in, and steal the actual hard disk where the files are stored, but it is not "convenient".

As I said using Douglas Adams quote, I consider the approach not easily accessible.

The script in question may be obtained, as always, either via download of compressed image from winbuilder.net (preferrable option only if complete package is desirable), or the script itself from the livexp server: http://livexp.boot-l...cesCombo.script.

Yep , but I did not want the latest RemovableDevicesCombo.script, I wanted BOTH the latest RemovableDevicesCombo.script AND the old usb_keyboard_mouse_hotplug.script for imperscrutable comparing needs.

There is NOT any issue for me, I can find usually what I want, and specifically that .script was NOT an issue at all, I was using it as a simple example, I was posing a "general" issue.

Since this is becoming a "mixed" keyboard+mouse+organization problem, I will make another example:
A few minutes ago I suggested an user on 911Cd to have a try with LiveXP and NativeEx:
http://www.911cd.net...showtopic=23431

Besides a link to the Board and Forum, to the "old" tables, and to the Amalux's Tutorial I wasn't able to give a "right" reference to NativeEx, apart from the site:
http://nativeex.boot-land.net/

I did a "simple" google search, i.e. a search like any "normal human being" would perform.

Results:
1st Result:
http://winbuilder.ne...s/nativeex.html
which says nothing and has a link to a (now) unresolved stoopid "friendly" name:
http://www.boot-land...LiveXP-f52.html
which resolves to the homepage of the Board:
http://www.boot-land.net/forums/
2nd Result:
http://winbuilder.ne...oad.php?view.27
with a link to here:
http://native.boot-land.net/
(where NO useful info is present)
and one to here:
http://www.boot-land...LiveXP-f52.html
(same unresolved "friendly" name)
and a link to an old download of an .exe (something that NOONE in his right mind would do, without knowing what the heck he/she is downloading)
3rd Result:
http://native.boot-l...t/downloads.htm
WOW, finally something working, a few links:
http://nativeex.boot.../nativeEx_Core/ <-Forbidden You do not have permission to access this document.
http://nativeex.boot...iveEx_barebone/ <-Forbidden You do not have permission to access this document.
http://nativeex.boot-land.net/Tools/ <-Forbidden You do not have permission to access this document.
http://nativeex.boot...LiveXP20070731/ <-Forbidden You do not have permission to access this document.
http://nativeex.boot-land.net/LiveXP/ <-Forbidden You do not have permission to access this document.
http://native.boot-l...dateCore.Script < a self referencing link, which leads nowhere
Then there is finally a working link:
http://www.boot-land.../WinBuilder.exe
which of course I wouldn't follow (I would never download a .exe file without actually knowing WHAT it is)
4th Result:
stoopid search engine like resume
5th Result:
stoopid search engine like resume
6th result:
http://www.boot-land...hp?showforum=83

Finally

Unfortunately first two or three attempt in the stickies all lead to one of the NOT working places already seen.

A "normal human being" at this point will likely give up, or even if he/she doesn't he will have formed a firm opinion on the fact that we are a bunch of clowns.

If you think this is the "right" way to manage things, you are very welcome , with my hat of "common user" on I feel anyhow allowed to say that the experience sucked.

As well, if I put on my hat of "janitor" I can see that's a BIG MESS, but being a S.E.P., I won't do anything about it (even where and if I could).

Please note that this is just another example, I personally disagree with a lot of things, it is nothing "particularly aimed" to this or that developer/project manager.

@Lancelot
What I would actually "like" to see is OF COURSE NOT:

I guess the "best" possible solution maybe at server side (if possible) so when we upload, server automatically renames the files that exists.! (Since we update scripts very frequently it would be very hard (&annoying&boring) to make this action manually each time for each script)
So when a user browse server he would get
UltraISO.script
UltraISO_200911041619.scriptOld
UltraISO_200911141123.scriptOld
UltraISO_200911260937.scriptOld
I guess this is what you want. Maybe better to ask Nuno.

But rather:

\LiveXP\
\LiveXP\Latest\ (or "Current") <-containing "latest" or "current" version, i.e. what Winbuilder users would get
\LiveXP\Archives\
\LiveXP\Archives\LiveXP_20091104\<-containing an integral copy as is of the "current" or "latest" directory how it was IMMEDIATELY before the update, i.e. what Winbuilder users would have gotten the day before
\LiveXP\Archives\LiveXP_20091114\
\LiveXP\Archives\LiveXP_20091115\

And, BTW, don't try to be smart with me , putting hours and minutes on a release means that the release is made BEFORE thinking , a single release a day is MORE than enough.



jaclaz

[Lancelot]

First of all, about nativeex:
I also know the missings of nativeex server links, as far as i know Peter likes to get more busy on producing utilities and scripts in his 40 hours of a day and he could not find to reorganise (or update) properly through topics. Well I learned to live with that and if i can not find something I ask Peter where to find so Peter fixes links....
Further comments should be made on nativeex section
About nativeex_barebone project: Peter as also being the senior developer of winbuilder wrote on various topics that nativeex project is a base project which he also tests new (and even unpublished) winbuilder versions. This may cause one to fail to build with nativeex_barabone and if that happens s(h)e should contact to Peter to get an updated ( trash ) version.
As a result It is better to advice any nativeex based project to new users where he could shrink down to the barebone limits

And, BTW, don't try to be smart with me

I really am not, You know I wrote before that you are one of my best known hero when i was googleing around searching for some specific tasks. At that times i never be a member of a forum and never asked questions on topics since I found lots of documents (& links ) from mostly you which i believed i have to study first (and studied and learned some of them (verry little compared with your great knowledge)... )
Shortly: You are absolutely more smart than me, I am just a turtle trying to understand things you write.

putting hours and minutes on a release means that the release is made BEFORE thinking , a single release a day is MORE than enough.

It is only a method decision, I do not care version numbers of scripts, when a bugy (even typo or little requirement etc) found i quickly upload new script. If i remember right i share the same idea with paraglider with this method. On the other hand there are some scripts I spend days & weeks to update....

Anyway going back to main subject:
Making daily (or every 3 days, every week etc) uploads of whole project is very unneccary and VERRRY hard for us.
Also there are things, first of all as far as I know, Galapo (the boss) do not save old copies of scripts , and I guess Fxscrpt do not save too.
I guess I am the only backup freak of the LiveXP project with a similar way of thinking like you (I save old scripts of project as much as i can),
** A feasable solution: I can share (and update frequently) my backup of old files on a single wb server (maybe \LiveXP\OLDFILES\). (currently about 2GB, besides I need time to check before uploading) It would help a lot to find old copies of scripts & files for the Finders who search for old files like you !!??

I hope you like the idea

[MedEvil]

Back on topic.
Just checked NPE with the usb pnp option, didn't work any different than before.
Moved the plug around trough all available sockets. Nothing!

It's a MB with an Intel P55 Express Chipset.

[was_jaclaz]

Back off topic.

I really am not, You know I wrote before that you are one of my best known hero when i was googleing around searching for some specific tasks. At that times i never be a member of a forum and never asked questions on topics since I found lots of documents (& links ) from mostly you which i believed i have to study first (and studied and learned some of them (verry little compared with your great knowledge)... )
Shortly: You are absolutely more smart than me, I am just a turtle trying to understand things you write.

It is only a method decision, I do not care version numbers of scripts, when a bugy (even typo or little requirement etc) found i quickly upload new script. If i remember right i share the same idea with paraglider with this method. On the other hand there are some scripts I spend days & weeks to update....

Don't put you too down.
You are a valid contributor to the Community and I know you are NOT the one to blame, the mere fact that you are trying to find or suggest a solution means several things:

• that you care about the problems
• that the problems exist
• that a solution is advisable (i.e. you have - definitely expressing it with far less grumpiness than me - an opinion not too far from mine: it's a MESS)

Anyway going back to main subject:
Making daily (or every 3 days, every week etc) uploads of whole project is very unneccary and VERRRY hard for us.

I do understand this, and as always the hypothetical "solution" was just an idea, a provocation to see if I could stir some consciences.

Also there are things, first of all as far as I know, Galapo (the boss) do not save old copies of scripts , and I guess Fxscrpt do not save too.

Waiter come taste this soup ....
http://www.imdb.com/...98/crazycredits

I guess I am the only backup freak of the LiveXP project with a similar way of thinking like you (I save old scripts of project as much as i can),
** A feasable solution: I can share (and update frequently) my backup of old files on a single wb server (maybe \LiveXP\OLDFILES\). (currently about 2GB, besides I need time to check before uploading) It would help a lot to find old copies of scripts & files for the Finders who search for old files like you !!??

I hope you like the idea

Unfortunately I do not.

I don't want you to do the cleaning, though I am sure that you would be a good janitor.

I am trying to ask people to avoid as much as possible the need for someone to clean after them.

As said, the stoopid usb .script was just an example, there are very few things in the world I could care less than peeking inside a (new or old) LiveXP .script, the point was simply IF I wanted/needed to, why it should have been made utterly difficult?

As well, the nativeex was just an example, I do know how much peter (psc) is busy, but you will have to agree that if you put a page online with a number of links to other places, links on MOST of which you have total and exclusive control, you should be careful before removing ALL the targets - as demonstrated the ONLY working link is to the one placed outside direct cotrol of peter (it is under direct control of Nuno that I guess only by chance did not remove that file or renamed the server or changed something else).

I do know from experience how difficult is to keep things tidy and with a minimum of easyness in accessibility, but what I am trying to evidence is that, no matter who is to blame, we are not "organized" in a clear way and a newcomer will have more difficulties than needed (and some will just give up), which is actually the opposite of what a Board (and a support one particularly) should be.

Back on topic:

Just checked NPE with the usb pnp option, didn't work any different than before.
Moved the plug around trough all available sockets. Nothing!

It's a MB with an Intel P55 Express Chipset.

I would try booting on that machine a "standard" LiveXP, just to see if it's a specific NaughtyPE problem or it is a specific "Intel P55 Express Chipset".

BTW, shouldn't you have noticed it , it seems like NPE is using an OLD .script.....





jaclaz