Jump to content











Photo
- - - - -

[tool] myNIC


  • Please log in to reply
168 replies to this topic

#1 pscEx

pscEx

    Platinum Member

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

Posted 01 September 2007 - 02:09 PM

The subtitle tells enough:

Here a screen shoot:
mynic2.2.6.gif
How it works:
  • Scan the registry for either
    • All network drivers
    • Ethernet only
  • Use corresponding *.inf to query files to copy
  • Write the script with the driver files attached
You can download it here.

Peter

#2 TheHive

TheHive

    Platinum Member

  • .script developer
  • 4165 posts

Posted 02 September 2007 - 07:14 AM

Tried it and when I tried to click on the create script it tells me Invalid Filename. I have it pointing to the same directory as the exe.

Name used is
Intel_PRO_100_VE_Ethernet_Driver

#3 pscEx

pscEx

    Platinum Member

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

Posted 02 September 2007 - 10:05 AM

Tried it and when I tried to click on the create script it tells me Invalid Filename. I have it pointing to the same directory as the exe.

Name used is
Intel_PRO_100_VE_Ethernet_Driver


Thanks for the report. :loleverybody:

I'll upload a new version which can write a log.
Please post the log and the *.inf file


Peter

#4 pscEx

pscEx

    Platinum Member

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

Posted 02 September 2007 - 02:21 PM

Version 1.0.3 in on the nativeEx server.
  • Option to create Log (myNIC.log in the myNIC directory)
  • If the Script Path field is empty the script is generated in the myNIC directory
  • If the Source CD Path field is not empty and 'Use' is checked, files to encode are searched in this order
  • in \I386 as uncompressed file
  • in \I386 as compressed file
  • in \I386\SPx.cab
  • in \I386\Driver.cab
  • local Windows sub directory, depending on type
myNic1.0.3.gif

Peter

#5 TheHive

TheHive

    Platinum Member

  • .script developer
  • 4165 posts

Posted 02 September 2007 - 06:15 PM

Redownload from first post and ran the program in its own folder. I then just clicked on the Make Script button and get an error about "invalid filename".
1.jpg

Log file is blank.


The myNic.ini

[General]

Script=

Source=

EthernetOnly=True

Log=True

ShowLog=True

SourceCD=True

Level=4


#6 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 02 September 2007 - 08:28 PM

How it works:

  • Scan the registry for either
    • All network drivers
    • Ethernet only
  • Use corresponding *.inf to query files to copy
  • Write the script with the driver files attached

Peter, why do you limit such an interesting program to just NICs?
Shouldn't work this just as weel with all other drivers?

:loleverybody:

#7 pscEx

pscEx

    Platinum Member

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

Posted 03 September 2007 - 06:55 AM

Peter, why do you limit such an interesting program to just NICs?
Shouldn't work this just as weel with all other drivers?

:loleverybody:


It is just a program to give food for PENetwork.

Smiley is working on a generell solution to transfer the frivers during build time to registry.

Peter

#8 pscEx

pscEx

    Platinum Member

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

Posted 03 September 2007 - 06:57 AM

Redownload from first post and ran the program in its own folder. I then just clicked on the Make Script button and get an error about "invalid filename".

Thanks, so the issue is appearing before the first log line.

I'll look for that, maybe encrease the log functionality.

Peter

#9 pscEx

pscEx

    Platinum Member

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

Posted 03 September 2007 - 07:13 AM

Redownload from first post and ran the program in its own folder. I then just clicked on the Make Script button and get an error about "invalid filename".

I found it:

The script name is derived from the driver name.
And your driver name a slash, which are not valid in a file name.

Before use, I'll check the file name and change if necessary.

Peter

#10 Nuno Brito

Nuno Brito

    Platinum Member

  • .script developer
  • 10545 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 03 September 2007 - 09:06 AM

Hi Peter - looks great! :loleverybody:

Downloaded the zipped file for testing (not sure if this was the latest binary)

TheHive mentions the "Invalid Filename" error because no values are set as default for "Script Path"

-----

I also subscribe to medEvil's request and scan other available drivers or create scripts for every available network device (on my case it only showed the wifi as default but I'd like to automatically create all these scripts)

-- Is it possible to include all drivers from the host machine? :w00t:

This would likely help to add all updated drivers that can effectively handle the hardware properly. (including a lot of network drivers not found on MS CD's - netXtreme Gigabit for example), of course it would help to disable the option to use source CD and just incorporate the drivers as default.




-----

Would it be possible to use the variable %target_sys%\Drivers instead of I386\System32\Drivers? :w00t: (defined under script.project on livexp)

This would make scripts project agnostic

:w00t:

#11 pscEx

pscEx

    Platinum Member

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

Posted 03 September 2007 - 09:32 AM

TheHive mentions the "Invalid Filename" error because no values are set as default for "Script Path"

The reason for TheHive's troubles was a slash in the name (Fixed, but not yet delivered).
Empty 'Script Path' defaults to the myNIC.exe directory.

I also subscribe to medEvil's request and scan other available drivers or create scripts for every available network device (on my case it only showed the wifi as default but I'd like to automatically create all these scripts)

I concentrate on network drivers out of 3 reasons:
  • Smiley is working on a universal solution
  • The driver can be installed by PENetwork
    (I already tried with my Intel 845G driver. I could not install it during boot time)
  • Many drivers (other than network) have strange INF structures, a little bit outside the M$ INF rules.
    They use there own install program. And it would be hard to follow the logic of such INFs.

-- Is it possible to include all drivers from the host machine? huh.gif

Wait for smiley

Would it be possible to use the variable %target_sys%\Drivers instead of I386\System32\Drivers? huh.gif (defined under script.project on livexp)

I'll make it an option.

Peter

#12 smiley

smiley

    Silver Member

  • .script developer
  • 905 posts
  •  
    Greece

Posted 03 September 2007 - 09:42 AM

I also subscribe to medEvil's request and scan other available drivers or create scripts for every available network device (on my case it only showed the wifi as default but I'd like to automatically create all these scripts)

-- Is it possible to include all drivers from the host machine? :loleverybody:

This would likely help to add all updated drivers that can effectively handle the hardware properly. (including a lot of network drivers not found on MS CD's - netXtreme Gigabit for example), of course it would help to disable the option to use source CD and just incorporate the drivers as default.


Hi Nuno,
I have already created a tool for this job which is almost complete. I think that this week it will ready to upload.

Would it be possible to use the variable %target_sys%\Drivers instead of I386\System32\Drivers? :w00t: (defined under script.project on livexp)

This would make scripts project agnostic


How will this help? :w00t:

#13 pscEx

pscEx

    Platinum Member

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

Posted 03 September 2007 - 11:34 AM

Version 1.0.4 available.
  • 'Network Card' which is used as script name, can be changed manually before 'Make Script'
  • Replace invalid characters in script name by '_'
    (TheHive's issue)
  • Non-Microsoft driver files can be read from Source (CD) Path
Peter

#14 Nuno Brito

Nuno Brito

    Platinum Member

  • .script developer
  • 10545 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 03 September 2007 - 01:40 PM

Hi Nuno,
I have already created a tool for this job which is almost complete. I think that this week it will ready to upload.
How will this help? :loleverybody:


Very good news too! :w00t:

We would be able to use the same script on other type of projects like the x64 bit install which might not use I386, adding drivers to another installed windows or using the same script on vistape since windows PE 2.0 seems to use XP drivers - better have a flexible script, don't you agree? :w00t:

#15 smiley

smiley

    Silver Member

  • .script developer
  • 905 posts
  •  
    Greece

Posted 03 September 2007 - 02:19 PM

Very good news too! :loleverybody:

We would be able to use the same script on other type of projects like the x64 bit install which might not use I386, adding drivers to another installed windows or using the same script on vistape since windows PE 2.0 seems to use XP drivers - better have a flexible script, don't you agree? :w00t:


:w00t: Your suggestions are very good but we need a mechanism to check if the script is compatible with a project. If we don't have such a mechanism it will create maaany problems. Thanks for the suggestions, but the script is almost done and to achieve what you ask will need many more hours of coding and testing. Right now I don't have much time.

That's why this script will work only under windows XP /2003 and the produced scripts should be used ONLY for projects that use windows XP /2003 as source. Maybe future versions will be compatible with other sources/hosts.

In a few days school starts and I have to consentrate on studying because I'm the last grade.
So I'm trying to complete it now that I have the time.


John

#16 TheHive

TheHive

    Platinum Member

  • .script developer
  • 4165 posts

Posted 03 September 2007 - 08:00 PM

Version 1.0.4 available.

  • 'Network Card' which is used as script name, can be changed manually before 'Make Script'
  • Replace invalid characters in script name by '_'
    (TheHive's issue)
  • Non-Microsoft driver files can be read from Source (CD) Path
Peter

This version seems to work properly.
MyNic.jpg

MyNic2.jpg
:loleverybody:

#17 pscEx

pscEx

    Platinum Member

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

Posted 04 September 2007 - 08:07 AM

This version seems to work properly.

Can you please post the resulting script?
Your driver is more complicated than that one I have (CoInstaller) , and I have no possibility to check on my PC.

Thanks.

Peter

#18 TheHive

TheHive

    Platinum Member

  • .script developer
  • 4165 posts

Posted 04 September 2007 - 08:22 AM

Intel® PRO_100 VE Network Connection.Script
Attached File  Intel_R__PRO_100_VE_Network_Connection.Script   19.07KB   283 downloads

#19 pscEx

pscEx

    Platinum Member

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

Posted 04 September 2007 - 08:25 AM

Intel® PRO_100 VE Network Connection.Script

Thanks :loleverybody:

As I assumed there is an issue. I'm working on it.

No need to test your script with a real burned CD.
It will not work.

Peter

#20 pscEx

pscEx

    Platinum Member

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

Posted 04 September 2007 - 11:54 AM

Version 1.0.5 available.
Fixed the issue I found with TheHive's driver
  • Added .CoInstallers files
  • Added ServiceBinary files from .Services
  • Added search in addidional sections <entry>.ntx86, <entry>.ntia64 and <entry>.ntamd64 files.
Peter

#21 TheHive

TheHive

    Platinum Member

  • .script developer
  • 4165 posts

Posted 04 September 2007 - 05:55 PM

Version 1.0.5 available.


1.jpg

Log
Attached File  myNic.zip   545bytes   369 downloads

Script
Attached File  Intel_R__PRO_100_VE_Network_Connection.Script   121.67KB   303 downloads

#22 pscEx

pscEx

    Platinum Member

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

Posted 04 September 2007 - 06:00 PM

Log
Script

Thanks!
Next bug to hunt!
I already saw the result. Now I have to look for the reason.

Peter

#23 pscEx

pscEx

    Platinum Member

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

Posted 04 September 2007 - 06:08 PM

Version 1.1.0 is available.

I hope it fixes the latest bug reported by TheHive.

@TheHive, thanks for your patience. :loleverybody:
I cannot test because the driver is not installed on my system.

Peter

#24 TheHive

TheHive

    Platinum Member

  • .script developer
  • 4165 posts

Posted 05 September 2007 - 06:33 AM

Attached File  Intel_R__PRO_100_VE_Network_Connection.Script   155.58KB   330 downloads


No errors where reported when testing v1.1.0
1.jpg


LOG
Attached File  myNic.zip   551bytes   336 downloads

#25 pscEx

pscEx

    Platinum Member

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

Posted 05 September 2007 - 07:50 AM

No errors where reported when testing v1.1.0


Thanks :loleverybody:

Can you try a nativeEx_barebone project with this script, PENetwork and OB1 to burn onto CD.
Test whether you have internet connection.

Peter




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users