Jump to content











Photo
- - - - -

[tool] myNIC


  • Please log in to reply
168 replies to this topic

#101 pscEx

pscEx

    Platinum Member

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

Posted 12 November 2007 - 02:00 PM

:cheers: That's the most stupid thing i've ever heared of!
Any idea why it occured? And how did you fix it?

:cheers:

Very simply:
There are two different ways to build the script depending on provider 'Microsoft' or not.

Because in my PC's NIC the driver provider is Microsoft, I had no chance to test the other way.
Therefore there was a very hidden bug, wich could not be detected by reading the code, only by stepping through the prog.

Today I patched my registry to tell my system that the provider is not Microsoft
And that was the way how I fixed.

Peter

#102 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7,687 posts

Posted 12 November 2007 - 02:08 PM

Very simply:
There are two different ways to build the script depending on provider 'Microsoft' or not.

No i ment, why are there two ways? How do they differ?
I never had any problem copying any file, be it M$ or not.

:cheers:

#103 pscEx

pscEx

    Platinum Member

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

Posted 12 November 2007 - 02:12 PM

No i ment, why are there two ways? How do they differ?
I never had any problem copying any file, be it M$ or not.

:cheers:

Try to write a myNIC clone.
When it runs correctly, you know it.

Peter

#104 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7,687 posts

Posted 12 November 2007 - 03:13 PM

Try to write a myNIC clone.
When it runs correctly, you know it.

Very helpful information! :cheers:

#105 pscEx

pscEx

    Platinum Member

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

Posted 12 November 2007 - 03:18 PM

Very helpful information! :cheers:

As helpful as your questions help to solve the current issue.

Peter :cheers:

#106 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7,687 posts

Posted 12 November 2007 - 03:29 PM

As helpful as your questions help to solve the current issue.

:cheers: My questions wern't ment to help you. Why should they? You said, you solved the problem.
I was just looking to learn something about another Windows weirdness.

:cheers:

#107 pscEx

pscEx

    Platinum Member

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

Posted 12 November 2007 - 03:36 PM

:cheers: My questions wern't ment to help you. Why should they? You said, you solved the problem.
I was just looking to learn something about another Windows weirdness.

:cheers:

Here some code:
if AnsiCompareText(provider, 'Microsoft') = 0 then

  begin

    if hasWinSource then

    begin

      source := srcDir + '\I386\';

      if not DirectoryExists(source) then

      begin

        tmp := 'Your driver is a Microsoft driver.' + #13#10 + 'But ';

        tmp := tmp + source + ' does not exist.' + #13#10;

        tmp := tmp + '"Source Path" is no Microsoft source CD!';

        if ExtLog then log(tmp);

        MessageBox(frmHandle, PChar(tmp), '', MB_ICONEXCLAMATION or MB_OK);

        System.Close(logHandle);

        exit;

      end;

      actInf := tmpDir + infName;

      infName := source + inf;

      c_infName := AnsiLeftStr(infName, Length(infName) - 1) + '_';

      if FileExists(infName) then

      begin

        log('Copying INF ' + infName + ' to ' + actInf);

        fileCopy(infName, actInf, extLog);

//        CopyFile(PChar(infName), PChar(actInf), false);

      end

      else if FileExists(c_infName) then

      begin

        log('Expanding INF ' + c_infName + ' to ' + actInf);

        StartWait('Expand', '"' + c_infName + '" "' + actInf + '"', tmpDir, true, false);

      end;

      tempFiles.Append(actInf);

    end

    else

    begin

      source := winDir + '\inf\';

      if doPatch then

      begin

        actInf := tmpDir + infName;

        log('Copy INF ' + source + inf + ' to ' + actInf);

        fileCopy(source + inf, actInf, extLog);

//        CopyFile(PChar(source + inf), PChar(actInf), false);

        tempFiles.Append(actInf);

      end

      else

      begin

        actInf := winDir + '\inf\' + infName;

        log('Using ' + actInf);

      end;

    end;

  end

  else

  begin

    if srcDir <> &#39;&#39; then

      source := srcDir

    else

      source := winDir + &#39;\inf\&#39;;

    if DirectoryExists(source + &#39;I386&#39;) then

    begin

      tmp := &#39;Your driver is a non-Microsoft driver.&#39; + #13#10 + &#39;But &#39;;

      tmp := tmp + source + &#39; exists.&#39; + #13#10;

      tmp := tmp + &#39;"Source Path" seems to be a Microsoft source CD!&#39;;

      if ExtLog then log(tmp);

      MessageBox(frmHandle, PChar(tmp), &#39;&#39;, MB_ICONEXCLAMATION or MB_OK);

      System.Close(logHandle);

      exit;

    end;

    if doPatch then

    begin

      actInf := tmpDir + infName;

      log(&#39;Copy INF &#39; + source + inf + &#39; to &#39; + actInf);

      fileCopy(source + inf, actInf, extLog);//        CopyFile(PChar(inf), PChar(actInf), false);      tempFiles.Append(actInf);    end    else    begin      actInf := source + inf;      log(&#39;Using &#39; + actInf);    end;  end;

Peter

#108 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7,687 posts

Posted 12 November 2007 - 04:08 PM

I don't get it, your program was trying to rip the inf files for M$ drivers directly from the CD? :cheers:

#109 pscEx

pscEx

    Platinum Member

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

Posted 12 November 2007 - 04:15 PM

I don't get it, your program was trying to rip the inf files for M$ drivers directly from the CD? :cheers:

I don't get it, which line tells you that? :cheers:

Peter

#110 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2,813 posts
  •  
    United States

Posted 12 November 2007 - 04:41 PM

Peter!!

(I don't mean to break this up :cheers: but...)

Breakthrough! I took your latest 2.1.9 to the same machine I tested on where all attempts failed (no changes to machine since test) and 2.1.9 works beautifully! From floppy and from HDD! Very cool! You must have been doing your 'magic' again :cheers:

Here's the results (script works on boot disk):



:cheers:

#111 pscEx

pscEx

    Platinum Member

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

Posted 12 November 2007 - 04:45 PM

Peter!!

(I don't mean to break this up :cheers: but...)

Breakthrough! I took your latest 2.1.9 to the same machine I tested on where all attempts failed (no changes to machine since test) and 2.1.9 works beautifully! From floppy and from HDD! Very cool! You must have been doing your 'magic' again :cheers:

Here's the results (script works on boot disk):



:cheers:

:cheers:

Thanks for your help and patience! :cheers:

Now I'm waiting for Edborg's results.

Peter

#112 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7,687 posts

Posted 12 November 2007 - 04:58 PM

I don't get it, which line tells you that? :cheers:

Peter

That you were 'talking' about a folder called i386 in your code, you also expand the inf.
Two things unneeded for expanded and installed drivers.

:cheers:

#113 pscEx

pscEx

    Platinum Member

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

Posted 12 November 2007 - 05:08 PM

That you were 'talking' about a folder called i386 in your code, you also expand the inf.
Two things unneeded for expanded and installed drivers.

:cheers:

As a result: Everything works fine and nobody knows you do not know why.
Two possibilities
  • read the code more carefully and try to understand it's copy flow correctly
  • try to live with that
Peter :cheers:



#114 pscEx

pscEx

    Platinum Member

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

Posted 12 November 2007 - 05:14 PM

@Edborg,

I see you in the forum.

Maybe caused by MedEvil's discussion items an important post is lost in the mass.

Please see post #99.

Peter

#115 edborg

edborg

    Frequent Member

  • .script developer
  • 370 posts
  •  
    Italy

Posted 12 November 2007 - 05:15 PM

:cheers:

Thanks for your help and patience! :cheers:

Now I'm waiting for Edborg's results.

Peter

Here I am!
Something changed... but still error :cheers:
edborg

Attached Thumbnails

  • MyNic2.1.9.jpg


#116 edborg

edborg

    Frequent Member

  • .script developer
  • 370 posts
  •  
    Italy

Posted 12 November 2007 - 05:20 PM

Well, not so bad!
With my other NIC (WiFi) it works :cheers: And this is not Microsoft, either.
I think you're almost there, congratulations, don't give up! :cheers:
edborg

Attached Thumbnails

  • MyNic2.1.9work.jpg


#117 pscEx

pscEx

    Platinum Member

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

Posted 12 November 2007 - 05:23 PM

Here I am!
Something changed... but still error :cheers:
edborg


That is a very strange new apperance.
Status line says: encoding :cheers:

Can you PM me the .inf and all 'CopyFiles' mentioned in the inf?

Peter

#118 pscEx

pscEx

    Platinum Member

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

Posted 12 November 2007 - 05:26 PM

Well, not so bad!
With my other NIC (WiFi) it works :cheers: And this is not Microsoft, either.
I think you're almost there, congratulations, don't give up! :cheers:
edborg

This seems also not to work!
The script only contains the inf, no sys or dll!

But WiFi is new for me ...

Peter

#119 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7,687 posts

Posted 12 November 2007 - 05:32 PM

Good thing at least you know why it works.
Oops, it doesn't!

#120 pscEx

pscEx

    Platinum Member

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

Posted 12 November 2007 - 05:46 PM

Good thing at least you know why it works.
Oops, it doesn't!

Once again: You have to use information more careful.

The issue now deals with 'Encoding', a dcu supplied by booty#1.
That is an issue which never came up until now.
And it has nothing to do with the i386 issue you think having found.

Peter

#121 edborg

edborg

    Frequent Member

  • .script developer
  • 370 posts
  •  
    Italy

Posted 12 November 2007 - 05:55 PM

This seems also not to work!
The script only contains the inf, no sys or dll!

But WiFi is new for me ...

Peter

Yes, I noticed that no sys was copied, but at least there was no blocking error.
Anyway, the following is REALLY strange to me, but it might mean something to you...
I'l try to explain:
I run 2.1.9, either successfully or unsuccessfully, depending on the NIC selected, it doesn't matter.
I then run the "old" 2.1.4 ... and it works for both NICs (only once, not the second time).
When I say "works" I mean it encodes something with no error message, not that I tested the resulting script.

There must be some setting which makes or makes not copying/editing possible.
I'm sure you'll find out. :cheers:
edborg

#122 pscEx

pscEx

    Platinum Member

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

Posted 12 November 2007 - 05:58 PM

Yes, I noticed that no sys was copied, but at least there was no blocking error.
Anyway, the following is REALLY strange to me, but it might mean something to you...
I'l try to explain:
I run 2.1.9, either successfully or unsuccessfully, depending on the NIC selected, it doesn't matter.
I then run the "old" 2.1.4 ... and it works for both NICs (only once, not the second time).
When I say "works" I mean it encodes something with no error message, not that I tested the resulting script.

There must be some setting which makes or makes not copying/editing possible.
I'm sure you'll find out. :cheers:
edborg

Can you post the different logs, and the infs including the syss and dlls?

Peter

#123 edborg

edborg

    Frequent Member

  • .script developer
  • 370 posts
  •  
    Italy

Posted 12 November 2007 - 06:23 PM

Can you post the different logs, and the infs including the syss and dlls?

Peter

Log and inf for the non working NIC (VIA) in 2.1.9 are enclosed. I hope it's useful.
I don't know which sys/dll are involved.

isNIC: True
(srcDir <> ''): False
hasWinSource: False
HomeDir: G:\Temp\
Script file: G:\Temp\VIA Rhine II Fast Ethernet Adapter.Script
Provider is 'Microsoft': False
Copy INF C:\WINDOWS\inf\oem32.inf to C:\DOCUME~1\EDB\LOCALS~1\Temp\oem32.inf
First numRead = 2048
First numWritten = 2048
Last numRead = 2039
Last numWritten = 2039
Blocks transferred: 31
Using inf file: C:\DOCUME~1\EDB\LOCALS~1\Temp\oem32.inf
Schedule for Encode: "C:\DOCUME~1\EDB\LOCALS~1\Temp\oem32.inf" to folder "Inf"
Start section: "VT3065.ndi"
Searching real entry sections:
Found: VT3065.ndi
Working with section: VT3065.ndi
Working with copy section: FET.ndi.CopyFiles
Schedule for Encode: "C:\WINDOWS\system32\winndi.dll" to folder "System"
Working with copy section: FET.SW.CopyFiles
Schedule for Encode: "C:\WINDOWS\system32\vuins16.dll" to folder "System"
Encoding scheduled files ...
Encoding "C:\DOCUME~1\EDB\LOCALS~1\Temp\oem32.inf" to "Inf"
Encoding "C:\WINDOWS\system32\vuins16.dll" to "System"

edborg

Attached Files



#124 pscEx

pscEx

    Platinum Member

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

Posted 12 November 2007 - 06:31 PM

Log and inf for the non working NIC (VIA) in 2.1.9 are enclosed. I hope it's useful.
I don't know which sys/dll are involved.

edborg


Thanks, Edborg!

I hope that is enough stuff do have an intersting evening!

I think, I really do not need the sys/dll. I'm going to copy and rename some files to them. (For debug, contents of the files does not matter, they just have to exist)

'See' you tomorrow!
Have a nice evening!

Peter

EDIT: One file I really need: vuins16.dll
Encoding seems to have troubles with it

#125 edborg

edborg

    Frequent Member

  • .script developer
  • 370 posts
  •  
    Italy

Posted 12 November 2007 - 06:48 PM

Thanks, Edborg!

I hope that is enough stuff do have an intersting evening!

I think, I really do not need the sys/dll. I'm going to copy and rename some files to them. (For debug, contents of the files does not matter, they just have to exist)

'See' you tomorrow!
Have a nice evening!

Peter

EDIT: One file I really need: vuins16.dll
Encoding seems to vave troubles with it

I see now vuins16.dll is in the log, but I don't have it in my (WinXP SP1) system. :cheers:
Might that be the reason of failure on my machine?
I have a vuins32.dll instead (enclosed, just in case).
I must go now, see you tomorrow.
edborg

Edit: Uplaod failed :cheers: Reuploaded zipped.

Attached Files






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users