168 replies to this topic

[pscEx]

Re-Re-tried.
And the only change now, believe me, is the version number.
edborg

ADDED
As I suspect you won't believe me ... here it is:

myNic version 2.2.2

 isNIC: True

 &#40;srcDir <> &#39;&#39;&#41;&#58; False

 hasWinSource&#58; False

 HomeDir&#58; G&#58;\Temp\

 Script file&#58; G&#58;\Temp\VIA Rhine II Fast Ethernet Adapter.Script

 Provider is &#39;Microsoft&#39;&#58; False

 Copy INF C&#58;\WINDOWS\inf\oem32.inf to C&#58;\DOCUME~1\EDB\LOCALS~1\Temp\oem32.inf

   First numRead = 2048

   First numWritten = 2048

   Last numRead = 2039

   Last numWritten = 2039

   Blocks transferred&#58; 31

 Using inf file&#58; C&#58;\DOCUME~1\EDB\LOCALS~1\Temp\oem32.inf

 Schedule for Encode&#58; &#34;C&#58;\DOCUME~1\EDB\LOCALS~1\Temp\oem32.inf&#34; to folder &#34;Inf&#34;

 Start section&#58; &#34;VT3065.ndi&#34;

 Searching real entry sections&#58;

   Found&#58; VT3065.ndi

   Found&#58; VT3065.ndi.NT

   Found&#58; VT3065.ndi.NT.Services

 Working with section&#58; VT3065.ndi

   Working with copy section&#58; FET.ndi.CopyFiles

	 Schedule for Encode&#58; &#34;C&#58;\WINDOWS\system32\winndi.dll&#34; to folder &#34;System&#34;

   Working with copy section&#58; FET.SW.CopyFiles

	 Schedule for Encode&#58; &#34;C&#58;\WINDOWS\system32\vuins16.dll&#34; to folder &#34;System&#34;

 Working with section&#58; VT3065.ndi.NT

   Working with copy section&#58; FET.CopyFiles.NT

	 Schedule for Encode&#58; &#34;C&#58;\WINDOWS\system32\drivers\fetnd5bv.sys&#34; to folder &#34;Driver&#34;

   Working with copy section&#58; FET.SW.CopyFiles.NT

	 Schedule for Encode&#58; &#34;C&#58;\WINDOWS\system32\vuins32.dll&#34; to folder &#34;System&#34;

	 Schedule for Encode&#58; &#34;C&#58;\WINDOWS\system32\difxapi.dll&#34; to folder &#34;System&#34;

 Working with section&#58; VT3065.ndi.NT.Services

   Checking&#58; FET.Service

	 Schedule for Encode&#58; &#34;C&#58;\WINDOWS\system32\drivers\fetnd5bv.sys&#34; to folder &#34;Driver&#34;

 Patching C&#58;\DOCUME~1\EDB\LOCALS~1\Temp\oem32.inf

 Encoding scheduled files ...

   Encoding &#34;C&#58;\DOCUME~1\EDB\LOCALS~1\Temp\oem32.inf&#34; to &#34;Inf&#34;

   Encoding &#34;C&#58;\WINDOWS\system32\difxapi.dll&#34; to &#34;System&#34;

   Encoding &#34;C&#58;\WINDOWS\system32\drivers\fetnd5bv.sys&#34; to &#34;Driver&#34;

 !!! File &#34;C&#58;\WINDOWS\system32\vuins16.dll&#34; does not exist&#34;

   Encoding &#34;C&#58;\WINDOWS\system32\vuins32.dll&#34; to &#34;System&#34;

 !!! File &#34;C&#58;\WINDOWS\system32\winndi.dll&#34; does not exist&#34;

 Deleting temporary files ...

   Deleted C&#58;\DOCUME~1\EDB\LOCALS~1\Temp\oem32.inf

   Deleted C&#58;\DOCUME~1\EDB\LOCALS~1\Temp\difxapi.arc

   Deleted C&#58;\DOCUME~1\EDB\LOCALS~1\Temp\fetnd5bv.arc

   Deleted C&#58;\DOCUME~1\EDB\LOCALS~1\Temp\vuins32.arc

Please repost your oem32.inf. Maybe mine is different (what is ratherr impropable)

What is the OS of the host where you are running myNIC?

@Edborg,
I think we are building 95 % of the forum's traffic today.
Let's make a break to think about different issues. And come back with fresh ideas.

Peter

[pscEx]

Please repost your oem32.inf. Maybe mine is different (what is ratherr impropable)
Peter

They seem to be different:
Your copy:

First numRead = 2048

   First numWritten = 2048

   Last numRead = 2039

   Last numWritten = 2039

   Blocks transferred: 31

My copy:

First numRead = 2048

  First numWritten = 2048

  Last numRead = 2039

  Last numWritten = 2039

  Blocks transferred: 29

Peter

[edborg]

Please repost your oem32.inf. Maybe mine is different (what is ratherr impropable)

What is the OS of the host where you are running myNIC?

You've already requested (and obtained) my oem32.inf.
Maybe the copy you have has already been altered by your program. Here is a fresh copy from my inf folder.

The host's OS is WinXP pro SP1 eng.
edborg

Attached Files

•  oem32.inf   59.99KB   452 downloads

[pscEx]

You've already requested (and obtained) my oem32.inf.
Maybe the copy you have has already been altered by your program. Here is a fresh copy from my inf folder.

They are really different.
I think, I anywhen patched the inf by mistake

Peter

[pscEx]

Version 2.2.3 available.

@Edborg: At least it generates a correct result.
You have to check whether it works in the PE.

@Amalux: Can you please check whether it still works for you.
For me it still works.

Peter

[edborg]

Version 2.2.3 available.

@Edborg: At least it generates a correct result.
You have to check whether it works in the PE.
...
Peter

I confirm that the script looks OK on my host, and the log as well, but I can't test it in the real PE for now.

What I can do, if you're willing to further investigate and refine your program, is to send you the script that has been generated by myNIC on my other PC and the one that I use there created with CreateDrivers.script (which works for me).
They differ quite a lot in size, as if myNIC either used a different .inf (which calls for a different .sys), or failed encoding some files...

I send you this info just in case it's helpful to you, but please don't do any further research for me.

edborg

Attached Files

•  Realtek_RTL8139_Family_PCI_Fast_Ethernet_NIC.Script   21.06KB   446 downloads
•  Driver_Realtek_RTL8139_810x_Family_Fast_Ethernet_NIC.script   62.92KB   572 downloads

[pscEx]

I confirm that the script looks OK on my host, and the log as well, but I can't test it in the real PE for now.

What I can do, if you're willing to further investigate and refine your program, is to send you the script that has been generated by myNIC on my other PC and the one that I use there created with CreateDrivers.script (which works for me).
They differ quite a lot in size, as if myNIC either used a different .inf (which calls for a different .sys), or failed encoding some files...

I send you this info just in case it's helpful to you, but please don't do any further research for me.

edborg

Something strange here:

CreateDrivers packs Rtlnic51.sys and oem21.inf into the script.
myNIC packs RTL8139.sys and netrtsnt.inf into the script.

Are you sure that the scripts are made on the same PC?

EDIT: Sorry, I should read more careful! You mentioned the different PC and driver!

Peter

[amalux]

Version 2.2.3 available.

@Edborg: At least it generates a correct result.
You have to check whether it works in the PE.

@Amalux: Can you please check whether it still works for you.
For me it still works.

Peter

Peter, I missed 2.2.3; 2.2.4 is (possibly) producing some strange behavior in my test machine. it will take a little while to sort out. I'll get results ASAP.

[amalux]

Peter, I missed 2.2.3; 2.2.4 is (possibly) producing some strange behavior in my test machine. it will take a little while to sort out. I'll get results ASAP.

Peter, I couldn't reproduce the 'bug' so it must have been coincidental and unrelated to MyNIC. 2.2.4 seems to work fine, here's the log:

I'll try it in a boot disc later today and confirm all is well with 'your baby'

[amalux]

Peter, I couldn't reproduce the 'bug' so it must have been coincidental and unrelated to MyNIC. 2.2.4 seems to work fine, here's the log:

I'll try it in a boot disc later today and confirm all is well with 'your baby'

OK, everything worked great! LiveXP booted 'test machine' using NIC driver script created with MyNIC 2.2.4.


(Couldn't post from LiveXP, 'Internal Server Error' )

EDIT: OK, now it's working; posting from here now (can't post images though, Opera?)

[pscEx]

As a result:

2.2.4 seems to satisfy all currently known requests

Peter

[amalux]

As a result:

2.2.4 seems to satisfy all currently known requests

Peter

Peter,

I thought it might be nice to have MyNIC included on a LiveXP disc! I created a script that seems to work OK but when I launch MyNIC from LiveXP, I get the following errors...


Any ideas on this? Here's the script I tested:

[pscEx]

Peter,

I thought it might be nice to have MyNIC included on a LiveXP disc! I created a script that seems to work OK but when I launch MyNIC from LiveXP, I get the following errors...


Any ideas on this? Here's the script I tested:

At least the second error:
When exiting, myNIC writes actual settings into myNIC.ini, to preserve them for the next start.

If you do not use BootSDI or FBWF, X: is read-only.

But I do not see the sence of having myNIC on the PE disk.
myNIC only detects installed NICs. Physically present hardware w/o installed ddriver is not detected.

Peter

[amalux]

At least the second error:
When exiting, myNIC writes actual settings into myNIC.ini, to preserve them for the next start.

If you do not use BootSDI or FBWF, X: is read-only.

But I do not see the sence of having myNIC on the PE disk.
myNIC only detects installed NICs. Physically present hardware w/o installed ddriver is not detected.

Peter

Peter,

Sorry, I assumed that the use of these PE discs for 'repair and recovery' on existing (damaged) OS installations was a given . A common scenario would be a clients machine (or mine) with an existing XP or 2000 installation that due to virus or other corruption is now unbootable (or unusable) from the HDD. PE boots the ailing machine from a CD drive, repairs the damage and everyone (except M$) is happy!

In the above scenario, if the machine has an installed NIC that the current PE build doesn't recognise; it would be helpful to grab the driver script for inclusion on future builds.

[MedEvil]

In your particular case, it would also be nice if you could make use of the driver that is on the damaged XP.

But this has nothing to do with Peters tool. It's ment to rip a drver from a working XP for later use in a PE.

[amalux]

In your particular case, it would also be nice if you could make use of the driver that is on the damaged XP.

But this has nothing to do with Peters tool. It's ment to rip a drver from a working XP for later use in a PE.

I get it now, thanks

[pscEx]

myNIC version 2.2.6 online.

Fixed bug with 'Index out of bounds'

Peter

[amalux]

myNIC version 2.2.6 online.

Fixed bug with 'Index out of bounds'

Peter

Thanks for the update Peter

The link in the first post should be fixed as that's where most people would expect to download

[pscEx]

The link in the first post should be fixed as that's where most people would expect to download

Thanks Amalux!

Done

Peter