Jump to content











Photo
- - - - -

[tool] myNIC


  • Please log in to reply
168 replies to this topic

#51 pscEx

pscEx

    Platinum Member

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

Posted 08 November 2007 - 06:31 PM

I've tried MyNic 2.1.4 (last version).
It detects Nics, but on my PC it can't even copy the inf from where it is (C:\Windows\inf) to a Temp dir to start with. :cheers:
What might be the reason?
edborg

By the way, the inf folder (hidden) is not shown when browsing for selecting the Source (CD) Path.


@Edborg!

Your post seems to be very similar to that one of Amalux.
Now, when having two users with this issue, we are a step nearer to the solution.

Unfortunatelly, I'm not able to reproduce on my system.

@Edborg, @Amalux:
Can you post more info about your hosts.
OS incl version /SP
screenshoots of the property (attrib > file also possible) of
  • Windows\inf
  • your inf file wich does not work
  • Temp folder
And whatever you think that it may be unique for your system

Thanks

Peter

#52 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 09 November 2007 - 06:47 AM

@Edborg!

Your post seems to be very similar to that one of Amalux.
Now, when having two users with this issue, we are a step nearer to the solution.

Unfortunatelly, I'm not able to reproduce on my system.

@Edborg, @Amalux:
Can you post more info about your hosts.
OS incl version /SP
screenshoots of the property (attrib > file also possible) of

  • Windows\inf
  • your inf file wich does not work
  • Temp folder
And whatever you think that it may be unique for your system

Thanks

Peter

Hi Peter!
XP Pro (2002) SP2 - I'll try to get those screenshots for you (tomorrow?) I've got that machine apart right now - The only unique thing about it is that it's a piece of junk! (got it free, so I can't complain) Dell Optiplex GX-260 - Intel Celeron 1.7Ghz; 512MB; nV6800 AGP; NIC on SB (Intel Pro 100 I think) I'll try and get more info tomorrow...

#53 edborg

edborg

    Frequent Member

  • .script developer
  • 387 posts
  •  
    Italy

Posted 09 November 2007 - 09:05 AM

@Edborg!

Your post seems to be very similar to that one of Amalux.
Now, when having two users with this issue, we are a step nearer to the solution.

Unfortunatelly, I'm not able to reproduce on my system.

@Edborg, @Amalux:
Can you post more info about your hosts.
OS incl version /SP
screenshoots of the property (attrib > file also possible) of

  • Windows\inf
  • your inf file wich does not work
  • Temp folder
And whatever you think that it may be unique for your system

Thanks

Peter

Quite strange!
The thing happens on two XP pro SP1 hosts (with different NICs, obviously).
So, it's neither the inf file, nor the inf folder (which is read-only, hidden), but the Temp folder, which is also read-only (why?) :cheers:
Moreover, if I remove the flag from the case (that is greyed but active) it gets read-only again the next time I check its properties. :cheers:
edborg

Added
Notwithstanding the greyed read-ony attribute of the temp folder, a batch file with the following command is executed normally:
copy "C:\Windows\inf\oem32.inf" "C:\Documents and Settings\EDB\Local Settings\Temp"
That is, the inf gets copied this way (though it shouldn't), and not your way (from myNIC.exe)!
:cheers: :cheers: :cheers:

After copying the inf manually and running myNIC.exe, a script is generated with no error messages (but the driver is not encoded, only the inf).

#54 pscEx

pscEx

    Platinum Member

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

Posted 09 November 2007 - 10:44 AM

The thing happens on two XP pro SP1 hosts (with different NICs, obviously).
So, it's neither the inf file, nor the inf folder (which is read-only, hidden), but the Temp folder, which is also read-only (why?) :cheers:


Good result!

A different thing I saw:

Your Temp path is in the short form. On my system it is the long form.

Can you try to change the Temp environment variable to the long form?

Peter

#55 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 09 November 2007 - 12:59 PM

Can you try to change the Temp environment variable to the long form?

I think, for that he needs to switch of the old 8.3 naming scheme.
On the other hand, your program shouldn't care about the difference.

:cheers:

#56 pscEx

pscEx

    Platinum Member

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

Posted 09 November 2007 - 01:39 PM

On the other hand, your program shouldn't care about the difference.

That's my opinion, too.

But before discussing what a program should be able to handle, I first want to find the reason why there is no copy at that place where it is assumed to be.

In the second step I'll tell my program to handle this correctly.

Peter

#57 pscEx

pscEx

    Platinum Member

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

Posted 09 November 2007 - 01:44 PM

There is a new version 2.1.5 available.
It writes a log even if the program crashes.

@Edborg, @Amalux:

Can you please use this version and post myNIC.log, which is created in the folder of myNIC.exe.

(Of course, 'Log' has to be checked in the GUI)

Peter

#58 edborg

edborg

    Frequent Member

  • .script developer
  • 387 posts
  •  
    Italy

Posted 09 November 2007 - 04:32 PM

Good result!

A different thing I saw:

Your Temp path is in the short form. On my system it is the long form.

Can you try to change the Temp environment variable to the long form?

Peter

I don't know how to do that! :cheers:
I used the command "set" to change Temp and Tmp (both the same), but they automatically returned as they were. :cheers:

I tested version 2.1.5, with the same result (log enclosed).
Besides the problem with myNIC.exe, how do you explain the temp folder being read-only (greyed), but allowing copying anyway?
edborg

#59 pscEx

pscEx

    Platinum Member

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

Posted 09 November 2007 - 04:37 PM

I don't know how to do that! :cheers:

I tested version 2.1.5, with the same result (log enclosed).
Besides the problem with myNIC.exe, how do you explain the temp folder being read-only (greyed), but allowing copying anyway?
edborg

Sorry, you forgot the log :cheers:

Peter

#60 pscEx

pscEx

    Platinum Member

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

Posted 09 November 2007 - 04:48 PM

Besides the problem with myNIC.exe, how do you explain the temp folder being read-only (greyed), but allowing copying anyway?

Greyed in Explored means 'hidden', not 'read-only'.

On my system I made it hidden. myNIC still works ok.

Peter

#61 pscEx

pscEx

    Platinum Member

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

Posted 09 November 2007 - 04:58 PM

I don't know how to do that! :cheers:
I used the command "set" to change Temp and Tmp (both the same), but they automatically returned as they were. :cheers:

I think it is currently not necessary, because my actual results go into a different direction.

But the way (I hope I translate my German captions into the correct English ones you can see. If not, try to find synonyms).
  • Right click 'My Computer'
  • Properties
  • Tab 'Extended' (or 'more' or 'Others' ...)
  • Button 'Environment Variables'
Here you can manage your user and the system wide variables.

There is a different way: Use setx instead of set. But setx is not part of all installations.

Peter

#62 edborg

edborg

    Frequent Member

  • .script developer
  • 387 posts
  •  
    Italy

Posted 09 November 2007 - 05:09 PM

Greyed in Explored means 'hidden', not 'read-only'.

On my system I made it hidden. myNIC still works ok.

Peter

Sorry for the missing log. I didn't notice that the server hadn't allowed the upload:
"Upload failed. You are not permitted to upload this type of file"
Here it is, anyway:
HomeDir: G:\Temp\

Script file: G:\Temp\VIA Rhine II Fast Ethernet Adapter.Script

Copy INF oem32.inf to C:\DOCUME~1\EDB\LOCALS~1\Temp\oem32.inf

Using inf file: C:\DOCUME~1\EDB\LOCALS~1\Temp\oem32.inf

Regarding read-only/hidden, I meant this:

Attached Thumbnails

  • Readonly.jpg


#63 edborg

edborg

    Frequent Member

  • .script developer
  • 387 posts
  •  
    Italy

Posted 09 November 2007 - 05:18 PM

I think it is currently not necessary, because my actual results go into a different direction.

But the way (I hope I translate my German captions into the correct English ones you can see. If not, try to find synonyms).

  • Right click 'My Computer'
  • Properties
  • Tab 'Extended' (or 'more' or 'Others' ...)
  • Button 'Environment Variables'
Here you can manage your user and the system wide variables.

There is a different way: Use setx instead of set. But setx is not part of all installations.

Peter

Thanks, Peter.
As you say setx is not recognized on my system, and set changes in a non persistent way.
Environment Variables in My Computer already appear in the long form, but their real value is %USERPROFILE%\Local Settings\Temp. Even after forcing them in the long form, they appear in the short form when running set at the command line.
edborg

#64 pscEx

pscEx

    Platinum Member

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

Posted 09 November 2007 - 05:29 PM

Sorry for the log. I didn't notice that the server didn't allow the upload:
"Upload failed. You are not permitted to upload this type of file"
Here it is, anyway:

HomeDir: G:\Temp\

 Script file: G:\Temp\VIA Rhine II Fast Ethernet Adapter.Script

 Copy INF oem32.inf to C:\DOCUME~1\EDB\LOCALS~1\Temp\oem32.inf

 Using inf file: C:\DOCUME~1\EDB\LOCALS~1\Temp\oem32.inf

Regarding read-only/hidden, I meant this:

The log line Copy ... tells that the WinAPI function CopyFile is done w/o troubles.
The log line Using ... tells us that myNIC in the next step reads the copied file
And because there is no one, crash ...

I'm going to replace the WinAPI copy by my own function. I already had to program it at a different place, but now I have to find it ...

I hope that I can publish version 2.1.6 today, but who knows ...

The greyed 'read-only' means that in this folder something, but not everything is read-only.

Peter

#65 pscEx

pscEx

    Platinum Member

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

Posted 09 November 2007 - 05:43 PM

I'm going to replace the WinAPI copy by my own function. I already had to program it at a different place, but now I have to find it ...

I hope that I can publish version 2.1.6 today, but who knows ...

I found it faster than assumed.
:cheers:
@Edborg
You can download and try version 2.1.6

Peter

#66 edborg

edborg

    Frequent Member

  • .script developer
  • 387 posts
  •  
    Italy

Posted 09 November 2007 - 05:51 PM

I found it faster than assumed.
:cheers:
@Edborg
You can download and try version 2.1.6

Peter

Perhaps to fast! :cheers:
Log:
HomeDir: G:\Temp\

Script file: G:\Temp\VIA Rhine II Fast Ethernet Adapter.Script

Attached Thumbnails

  • MyNic2.1.6.jpg


#67 pscEx

pscEx

    Platinum Member

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

Posted 09 November 2007 - 06:14 PM

Perhaps to fast! :cheers:
Log:

HomeDir: G:\Temp\

 Script file: G:\Temp\VIA Rhine II Fast Ethernet Adapter.Script


No, the procedure works.
But look into the status bar:
It tells that a copy has to be made.
And the error is 'File not found'. Why?

Bill G. says nothing about that. My procedure crashes. I this special case my proc is better (inspite it should not crash).

I make a new version with some logs during fileCopy.

Can you please make sure that oem32.inf really exists in %SystemRoot%\inf.

Peter

#68 edborg

edborg

    Frequent Member

  • .script developer
  • 387 posts
  •  
    Italy

Posted 09 November 2007 - 06:30 PM

-----
Can you please make sure that oem32.inf really exists in %SystemRoot%\inf.

Peter

YES IT DOES! Of course this has been my first check since the beginning. :cheers:
edborg

#69 pscEx

pscEx

    Platinum Member

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

Posted 09 November 2007 - 06:38 PM

@Edborg
@Amalux

If you both have a W2000 host I found it.

But in this case: I'm rather disappointed that you did not post it on my question about OS / SP etc.

Before I do prog changes, I'm waiting for an W2000 answer.

Peter

#70 edborg

edborg

    Frequent Member

  • .script developer
  • 387 posts
  •  
    Italy

Posted 09 November 2007 - 06:45 PM

@Edborg
@Amalux

If you both have a W2000 host I found it.

But in this case: I'm rather disappointed that you did not post it on my question about OS / SP etc.

Before I do prog changes, I'm waiting for an W2000 answer.

Peter

NO, Windows XP pro SP1, as already posted!
edborg

#71 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 09 November 2007 - 07:03 PM

@Edborg
@Amalux

If you both have a W2000 host I found it.

But in this case: I'm rather disappointed that you did not post it on my question about OS / SP etc.

Before I do prog changes, I'm waiting for an W2000 answer.

Peter

Peter!

See my post #52! - WinXP Pro (2002) SP2 (I do not have a Win2k machine setup right now)

I'm getting a bit lost on this thread :cheers: , sorry if this isn't what you want but here is some more info:

Note there is no oem1.inf in the Temp folder!



Log:

HomeDir: C:\mynic215test1\
Script file: C:\mynic215test1\Intel® PRO_1000 MT Network Connection.Script
Copy INF oem1.inf to C:\DOCUME~1\KYLEC~1\LOCALS~1\Temp\oem1.inf
Using inf file: C:\DOCUME~1\KYLEC~1\LOCALS~1\Temp\oem1.inf


I've got the machine setup now, I can respond quicker when you need test results!

OK, here's more...


#72 pscEx

pscEx

    Platinum Member

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

Posted 09 November 2007 - 08:14 PM

See my post #52! - WinXP Pro (2002) SP2 (I do not have a Win2k machine setup right now)
I'm getting a bit lost on this thread :cheers:

Thanks and Sorry :cheers:
I'm currently working on so many different topics that I overview that.

It is really a W2000 host issue.

And the differences are a mass ...

I'm working on this and I'm sure to have a myNIC.exe tomorrow, which also runs on W2000.
:cheers:

Peter

#73 pscEx

pscEx

    Platinum Member

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

Posted 09 November 2007 - 08:43 PM

myNIC version 2.1.7 is available.

I hope that it runs on W2000, too (and still runs on XP)

Peter

#74 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 09 November 2007 - 10:24 PM

myNIC version 2.1.7 is available.

I hope that it runs on W2000, too (and still runs on XP)

Peter

Peter!

I'm a bit confused; I don't know about the W2000 issue but as for XP, no improvement with 2.1.7 :cheers: , sorry. My last post still applies.

Let me know if you need any tests run on XP!
:cheers:

#75 pscEx

pscEx

    Platinum Member

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

Posted 09 November 2007 - 10:40 PM

Peter!

I'm a bit confused; I don't know about the W2000 issue but as for XP, no improvement with 2.1.7 :cheers: , sorry. My last post still applies.

Let me know if you need any tests run on XP!
:cheers:


Oops :cheers:
You are running on XP SP1 and there seem to be different issues between XP SP1 and W2000

(I hope I can install SP1 anywhere to test)

Thanks for your information. I'll check tomorrow.

Peter




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users