Need help with drivers on LiveXP
#1
Posted 22 June 2007 - 09:38 AM
I have a big problem: I have to create a PE for three(or four) different Computers and this would be ok, but I can't add the NIC-Drivers into the build. I've tryed it with the Qemu Network Driver script, the PENetwork script by Holger Kotsch, both at a time and even tryed to write a script by myself ( I'm a real newbie in this). The log shows no errors with the files and the Image is running on qemu AND on one of the Computers, where I need the PE, but when I start PENetwork I can't choose a Network adapter.
Is there someone who can help me with this???
Here's the link to the log file:log.rar
Had to upload it on Imgwelt.com, because it didn't work here.
#2
Posted 22 June 2007 - 09:52 AM
Hey Chief!Hello everybody!
I have a big problem: I have to create a PE for three(or four) different Computers and this would be ok, but I can't add the NIC-Drivers into the build. I've tryed it with the Qemu Network Driver script, the PENetwork script by Holger Kotsch, both at a time and even tryed to write a script by myself ( I'm a real newbie in this). The log shows no errors with the files and the Image is running on qemu AND on one of the Computers, where I need the PE, but when I start PENetwork I can't choose a Network adapter.
Is there someone who can help me with this???
Here's the link to the log file:log.rar
Had to upload it on Imgwelt.com, because it didn't work here.
You use [WinBuilderVersion=068 - CHIP edition]
You should download the latest stable version 070. I recommend to try 071 beta 5d.
Drivers:
The PE needs the 3 different NIC drivers as delivered by the manufacturer.
Copy *.inf to the i386\inf folder.
Copy *.sys to the i386\system32\drivers folder.
Copy everything else to the i386\system32 folder.
Then the PENetwork should recognize and use the driver which is suited for the individual PC.
The copy should be made by a script. So you have to create 3 scripts for the 3 different drivers.
Peter
#3
Posted 22 June 2007 - 09:58 AM
So you have to create 3 scripts for the 3 different drivers.
Won't it work, when i write only one script for all three drivers?? I need them all in one Build.
#4
Posted 22 June 2007 - 10:03 AM
If you want you can put all three into one script.Won't it work, when i write only one script for all three drivers?? I need them all in one Build.
But the 'standard' way is to have a different script for a different driver.
When building the project you select all three.
Peter
#5
Posted 22 June 2007 - 10:11 AM
Beside a little question: I've downloaded the 070 stabel and can I simply copy my project files into the 070 directory or do i have to write my scripts again??
#6
Posted 22 June 2007 - 10:14 AM
Ah, ok. I'll do so.
Beside a little question: I've downloaded the 070 stabel and can I simply copy my project files into the 070 directory or do i have to write my scripts again??
Yes, you can simply copy.
Peter
BTW I'm going to move this topic to the 'Support' forum
#7
Posted 22 June 2007 - 10:48 AM
My next PENetwork-script version 019 version I will put definitly to the LiveXP-project cause the version 011 in this project is too old.
One of my never versions has the possibility to take all drivers files from a selected folder (also takes files from subfolders).
It makes some things easier.
So long...
Holger
P.S. should be ready in the evening (it is already finished but not uploaded).
#8
Posted 22 June 2007 - 11:17 AM
One of my never versions has the possibility to take all drivers files from a selected folder (also takes files from subfolders).
It makes some things easier.
I've tryed it. It didn't work. It copied the files but when i've tested my PE, PENetwork couldn't see the devices.
#9
Posted 22 June 2007 - 11:20 AM
Did you burn a CD and tested with boot from CD?I've tryed it. It didn't work. It copied the files but when i've tested my PE, PENetwork couldn't see the devices.
If you use an emulator, PENetwork only detects the emulator's driver (If you activated the corresponding driver's script).
Peter
#10
Posted 22 June 2007 - 11:26 AM
Did you burn a CD and tested with boot from CD?
Yes I did.
And I selected the qemu driver too and he has not detected the network adapter of the emu.
#11
Posted 22 June 2007 - 11:59 AM
Yes I did.
And I selected the qemu driver too and he has not detected the network adapter of the emu.
Remove the Go2PDF script from the build.
I remember that there have been troubles between Go2PDF and PENetwork.
BTW: The best way is to start with a minimized Project.
If that works correctly add apps.
Maybe you try with nativeEx_barebone.
Peter
#12
Posted 22 June 2007 - 03:12 PM
#13
Posted 22 June 2007 - 06:53 PM
I'm working right now on this bug - found a solution and making some tests now...
I hope I'm finish these in the later evening so I can publish a new script with some other fixed bugs...
#14
Posted 23 June 2007 - 04:33 PM
I saw in the PENetwork script that it inserts drivers, too. But it also didn't work, or i've done something wrong. But as I said iwill try it again monday.
#16
Posted 25 June 2007 - 08:48 AM
That is an issue you could find by yourself, just by looking into the logSo here's my last log. I hope someone can help me.
There are error messages like
FileCopy - Failed to copy [%scriptdir\dr1\ipfnd51.sys] to: [F:\PE\winbuilder#$s070\Target\LiveXP\i386\system32\drivers\]You see the missing % at the end of %scriptdir ?
Peter
#17
Posted 25 June 2007 - 10:03 AM
#18
Posted 25 June 2007 - 10:25 AM
Maybe I will recheck it later in the evening....
#19
Posted 25 June 2007 - 10:28 AM
In the result there is no difference whether the drivers are copied by PENetwork or a (correct working) script.Ah ok. Now I see. But with the PENetwork; There is that part where is said that if you want drivers to be copied then enter the path. I've tryed it and it didn't work. Can someone tell me why??
Copy all drivers, infs, help files etc. into one directory and choose this directory inside the PENetwork GUI.
Peter
#21
Posted 27 June 2007 - 01:58 PM
I hope this brings "some clear air into the room".^^
#22
Posted 28 June 2007 - 02:37 PM
Any ideas, what i should do to solve it completely?? I have only 5 weeks to build a complete running LiveXP which supports network. Everything what my boss needs is done except of the Network.
Could anyone help me??? Please.
Here's the log:Log.rar
#23
Posted 28 June 2007 - 03:14 PM
Maybe I'm missing something but for a network card is buildin?
Thanks
Holger
#24
Posted 28 June 2007 - 06:19 PM
@Chief Aramaki:Could anyone help me??? Please.
I have some troubles to understand your behaviour:
You urgently ask (again) for help.
On the other hand you seem to try to manage how the help has to be.
- In post #11 I suggested to debug with a minimized project, maybe with nativeEx_barebone.
- Result: Your project still contains 40 SATA drivers, really unnecessary to solve the NIC issue!
- In post #16 I debugged your script, so finally the driver was really copied into the target. The files are in the target now!
- Result: You try to get the same result by using PENetwork copy mechanism
- Now Holger is (unnecessarily) asking for the copy log.
@Chief Aramaki:I have only 5 weeks to build a complete running LiveXP which supports network. Everything what my boss needs is done except of the Network.
In this forum, I really do not like text like this one.
You are trying to give your personal commercial pressure to people, who work here for fun, without any commercial interest.
If you have to fullfill a certain end date, you have to ask professional developers (like me ).
@Holger:
Maybe there is an issue with installing the driver: In my opinion in a PE environment the UpdateDriverForPlugAndPlayDevices call does not need the INSTALLFLAG_READONLY flag.
(I'm thinking on INSTALLFLAG_FORCE), maybe with SetupDiGetClassDevs having no DIGCF_PRESENT.
I suggest to experiment with reasonable different settings and send a set of test scripts to Chief Aramaki. (Unfortunatelly you cannot test, if you do not have the hardware).
Peter
#25
Posted 28 June 2007 - 06:51 PM
I've tryed it with the Qemu Network Driver script, the PENetwork script by Holger Kotsch, both at a time and even tryed to write a script by myself ( I'm a real newbie in this).
Your first post is a long time ago.
Just to make sure that in the mean time you understood the functionality:
In the following I'm speaking only about network drivers
First: There are several different drivers. Your PE needs the driver suited for the booted system:
- If you test in qEmu, you (only) need the qEmu NIC driver
- If you test in VirtualBox, you (only) need the VirtualBox NIC driver
- ...
- If you boot on a Compaq nw8440, you (only) need the Broadcom Ethernet NIC NetXtreme driver version 10.24d
Sorry, if this explanation has been below your level. But I have some doubts about the correct understanding
Peter
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users