1937 replies to this topic

[pscEx]

So that seems not to be only a question for Holger, but also a question for the 'project management'?

Just a crazy idea:

What about including and excluding the corresponding NICs depending on the selected emulator?

Peter

[Lancelot]

but also a question for the 'project management'?

you already know the answer, sadly 'project management' missed her major galapo. I am only a mini helper around for LiveXP and aware that definately not qualified to manage a project (especially LiveXP).
I try to do things as far as i know and still learning.

I dont know the reason, but my tests shows issue solved after updating "5 - CopyAndExpand.Script" to v22 , currently available on livexp server.

[pscEx]

I am only a mini helper around for LiveXP and aware that definately not qualified to manage a project (especially LiveXP).
I try to do things as far as i know and still learning.

You never know what you can do, before you tried it!

Peter

[pscEx]

I dont know the reason, but my tests shows issue solved after updating "5 - CopyAndExpand.Script" to v22 , currently available on livexp server.

Maybe we do a break for a week, get new power, and continue then!

I was going to test the latest LiveXP version (including the Copy&expand 22).
I did a download of 'Everything new'

The PE started with "Bootdisk expired" and asked me for a password

Peter

[Lancelot]

The PE started with "Bootdisk expired" and asked me for a password

you enabled sth you shouldnt, probably a mistake when clicking by mouse (i love my keyboard style on wb )

anyway
Solution probably is: disable shell security script before building (Basic--->Shells--->Explorer tweaks--->Shell Security) which is not selected as default (check here )

[pscEx]

you enabled sth you shouldnt, probably a mistake when clicking by mouse (i love my keyboard style on wb )

anyway
Solution probably is: disable shell security script before building (Basic--->Shells--->Explorer tweaks--->Shell Security) which is not selected as default (check here )

I did so, and I'm proud(?) to tell you, that still some is working.
Also with C&E version 22 / VirtualBox no running network in the PE.

Peter

[Lancelot]

Peter

Is there any reason to keep these values empty on PE !?

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders]
"Common AppData"
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders]
"AppData"

if not, should i do it with a seperate script or what you suggest..... ????

ps: i will look forward on lan issue tomorrow, enough for today .

[pscEx]

Peter

Is there any reason to keep these values empty on PE !?

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders]
"Common AppData"
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders]
"AppData"

if not, should i do it with a seperate script or what you suggest..... ????

ps: i will look forward on lan issue tomorrow, enough for today .

For me it is also enough for today.

But I think that these reg keys are filled out by nativeEx core. If not: Today is Day!

Peter

[Lancelot]

filled out by nativeEx core.

not sure about the meaning of filled out
according to babylon:
fill out: complete, answer (form, application)
also checked with google translator

If there should be values written in keys (just checked with current nativeex barabone), no values written, so i guess Today is day

Now enought to me with issues too, cu tomorrow

[pscEx]

not sure about the meaning of filled out

Ask babylon for [German] ausfüllen.
Here we have the lack of (our both) English knowledge.
Your Computer translations are correct.

It means: Write into the empty, predefined text box.

And simply: "define value"

Peter

[Lancelot]

Today definately is day

[fxscrpt]

Oh ...
I started with LiveXp minimum 'as is'.
Everything is ok except mmc.script.
There is one missing file: msimg32.dll.

Added file to mmc.script v.29

to be continued...

Edit:

virtual box nic problems:
oem3 (vmware nic) and virtual box nic have exactly
same pnp id

nic in virtual box:
PCI\VEN_1022&DEV_2000&SUBSYS_20001022&blabla

hwpnp selects best compatible driver from
oem3.inf (vmware nic) vmxnet.sys, but virtual box needs
generic pcntpci5.sys from netamd2.inf.
PCI\VEN_1022&DEV_2000

i dont think it's hwpnp problem,
because driver selection is ok.

Disable vmware nic driver if runnig vbox
or
remove vmware nic driver
(vmware can use generic pcntpci5.sys driver from netamd2.inf)
or
disable hwpnp
(Penetwork will select generic pcntpci5.sys driver)


to be continued...



Peter

Attached Files

•  MMC.script   41.45KB   517 downloads

[Lancelot]

fxscrpt

new mmc on server

[fxscrpt]

fxscrpt

new mmc on server

thanks. less trouble

Peter

[Lancelot]

disable hwpnp
(Penetwork will select generic pcntpci5.sys driver)

This is one of the reason i didnt notice with my custom mini test builds. (dont use hwpnp ruonce options to make faster trials) . Thanks clearing that out.

hwpnp selects best compatible driver from
oem3.inf (vmware nic) vmxnet.sys, but virtual box needs
generic pcntpci5.sys from netamd2.inf.
PCI\VEN_1022&DEV_2000

With livexp recommended download,
unselecting - VMWareNIC.script
selecting +VirtualBoxNIC_AMD_PCNET.script
results:
network running on qemu and vmware, but not virtualbox
(***oem3.inf is not in the build as it is in unselected VMWareNIC.script )


On the other hand with a 2nd trial:
making a custom small build with livepx (here is log to show which scripts selected etc, (on penetwork WindowsXP-KB918997-v6-x86-ENU.exe selected))
-VMWareNIC.script +VirtualBoxNIC_AMD_PCNET.script +hwpnp runonce
network running on all emulators (qemu, vmware and virtualbox !?)



So there is still another to kill




qemu special note:
on this 2nd trial qemu stuck with hwpnp screen "Root\*PNP0700\1_0_13_0_0_0"
i hope paraglider makes an esc button for hwpnp in future release, same hang issue happened a ~month ago on realpc too which i reported here.
Also i remember once loong time ago when we introduced hwpnp script first and make runonce selected default, there was same problem with qemu, but cant remember how fixed...
For now to get over this problem on qemu, on qemu script, select bochs bios and unselect "Disable Acpi" option (ps: note to fxscrpt: i love options :) )






I change the state of VirtualBoxNIC_AMD_PCNET from complete to minimum on LiveXP server, so trials with livexp can easly include this script. (besides, i believe it should be at first place in minimum state)
Also for now to prevent new livexp starters getting a hang on qemu in any package i changed selected false .

VirtualBoxNIC_AMD_PCNET.script v6 on livexp server now

cu tomorrow


Edit "qemu special note":
bochs bios is not necessary, only unselecting "Disable Acpi" option is enough. selected Normal bios and unselected "Disable Acpi" are the settings of the qemu script (for a long while) in livexp project

[pscEx]

fxscrpt

new mmc on server

on nativeEx server, too!

Peter

[Lancelot]

2nd found

+VirtNet Network Adapter.script +VirtualBoxNIC_AMD_PCNET.script + hwpnpruonce ---> Virtualbox network not working

New scripts uploaded to livexp server with the changes below:
VirtNet Network Adapter.script --> added disable... + selected false
VirtualBoxNIC_AMD_PCNET.script ---> added disable... + selected true
VMWareNIC.script ---> selected false (no need for that as default)

==> as a result at \Drivers\3 Network\ section only these 2 scripts selected
qEmuNIC_RTL8139.script
VirtualBoxNIC_AMD_PCNET.script
which makes all 3 popular emulators (qemu, virtual box, vmware) network run smoothly for new downloaded livexp.

ps:
Yep i dont know reason of The 2nd , but i am sure masters will clear out the reason


Edited

[pscEx]

Congratulations!

Now there is the same configuration like in (the allways 3-emulators ready) nativeEx_barebone.

Peter

BTW: Maybe it is now time to again think about my topic 'LiveXP - Factory settings'. It is really not the best idea to include 'Everything selected'

[Lancelot]

and to kill 1st described by fxscrpt, i now add disable functions to
VirtualBoxNIC_AMD_PCNET.script v8
VMWareNIC.script v3
available on LiveXP server

Now there is the same configuration like in (the allways 3-emulators ready) nativeEx_barebone.

a question for the nativeex barabone 'project management'?

(red added by me)

BTW: Maybe it is now time to again think about my topic 'LiveXP - Factory settings'. It is really not the best idea to include 'Everything selected'

on the other hand, we catch network bugy with that , anyway lets not rediscuss, lots of todo around .
but more important, as pointed out in your topic, this reminds me the need of ESC button on hwpnp in case of emergency (maybe you can pm paraglider, very easy to reproduce)

[pscEx]

BTW: Maybe it is now time to again think about my topic 'LiveXP - Factory settings'. It is really not the best idea to include 'Everything selected'

On the other hand, we catch network bugy with that

Maybe someone can explain me this logic:

• Put a couple of unneeded scripts into a project:
  A certain script fails
• Remove the unneeded scripts:
  The previously not running script now runs
• Tell the world: Introducing the bug gave me the possibility to fix it!
  Everything is running now, and nobody knows why!

@ALL
Please tell me, who needs (and for what) the scripts

• VirtNet Network Adapter.script
• VMWareNIC.script
  (VirtualBoxNIC_AMD_PCNET.script delivers a VMWare Ethernet Driver, look at the description)

Peter

[pscEx]

Now there is the same configuration like in (the allways 3-emulators ready) nativeEx_barebone.

a question for the nativeex barabone 'project management'?

(red added by me)

Thanks for the applause!

As to be seen, nativeEx_barebone from the very beginning works well with the three popular emulators.

Peter

[Lancelot]

As to be seen, nativeEx_barebone from the very beginning works well with the three popular emulators.

yep i know, just smile

(VirtualBoxNIC_AMD_PCNET.script delivers a VMWare Ethernet Driver, look at the description)

as i wrote before, that is the reason for having only these 2 scripts selected default by livexp now
qEmuNIC_RTL8139.script
VirtualBoxNIC_AMD_PCNET.script

Maybe someone can explain me this logic:
...
Please tell me, who needs (and for what) the scripts

Removing scripts from livexp came to my mind too, but similarly I asked galapo for the removal of QemuNIC-W2k3.script , as far as i remember his answer was that these scripts were on the project when he first came... With decision to think the same way to our project boss i decide to pospone the removel of scripts and protect users for selecting scripts in a wrong way.

Lets not stuck with this and change the mood Peter psc , died and now celebration time

Any progress with AppData key ?!

[pscEx]

Any progress with AppData key ?!

You continously ignore that I'm an old man and my memory is starting with 'today morning'

What's AppData key?

BTW: I'm going to write some new concerns into 'factory settings'. Try to make the best of it!

Peter

[Lancelot]

You continously ignore that I'm an old man and my memory is starting with 'today morning'

very sorry

What's AppData key?

empty values on PE at
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders]
"Common AppData"
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders]
"AppData"

and you answered:
But I think that these reg keys are filled out by nativeEx core. If not: Today is day

and i understand with "filled out" it means there should be values in these keys...(story ended at that point)..

[pscEx]

Here the shell folders created under nativeEX_barebone:

?

?
or a new 'conflict of interests' by some LiveXP scripts which do not like each other?
?

Peter