Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

Why this INF is not recognised?

- - - - -

  • Please log in to reply
8 replies to this topic

#1
MrMateczko

MrMateczko

    Newbie

  • Member
  • 16 posts
  • Joined 29-June 13
  • OS:none specified
  • Country: Country Flag

I have a Lenovo IdeaPad Z510 laptop with an Intel i3-4000M, and 8GB of RAM. It has a Realtek 8106E Fast Ethernet chip, and one of its compatible Hardware ID is this: PCI\VEN_10EC&DEV_8136&REV_07

The drivers for this are here: http://www.realtek.c...3&GetDown=false

This ID is present in the Win 2000/XP driver inside the .inf.

But, this very .inf is very similar to the Win98SE .inf, (it has all the stuff from the .inf from the Win98SE driver: strings, hardware ids, file destinations, driver options, etc.) but it's not recognized by Win98SE.

Here's the Win 2000/XP to look at:

http://wklej.org/id/1498595/

In the .inf for the Win98SE driver, there's no ID for my chip, but it's recognized by Win98SE. There's the Win98SE inf:

http://wklej.org/id/1498598/

 

So anyone can help me to get the Win2000/XP .inf to get recognized?

And no, the NDIS driver didn't work as an alternative, it is automatically disabled in the ASD.EXE, it says there's a conflict between the NDIS driver and the TCP/IP protocol.


Edited by MrMateczko, 25 October 2014 - 08:46 AM.



How to remove advertisement from MSFN

#2
jumper

jumper

    2014 All-American Masters HJ'er

  • Member
  • PipPipPip
  • 493 posts
  • Joined 21-January 11
  • OS:98SE
  • Country: Country Flag
The XP .inf file is about 16x too big for 9x to recognize. Try deleting everything that is clearly not needed, then run it through minf to reduce the size to below 64KB and see if 9x will recognize it then.

I'll compare the two files and report back later with my findings. These are all-in-one driver packages, however, so there probably isn't an actual 8106E driver file in the 9x package and the one in the NT package probably won't work in 9x.
Design feedback requested:
IHAtool - IpHlpApi tester; call various functions and report results
--status-> framework is solid; 22 api's fully supported; preview release coming soon
ComDlg32 wrapper - ComDlgEx meets IpHlpApi wrapper
--status-> PrintDlgExW working in latest SumatraPDF 8^)
Future projects: ImportPatcher40 - dialog interface; Kexter - IP40+Ktree+Kexstubs

#3
MrMateczko

MrMateczko

    Newbie

  • Member
  • 16 posts
  • Joined 29-June 13
  • OS:none specified
  • Country: Country Flag

Well...the file that is supossedly used by 98 section the inf is the Rtenic.sys.

But the same file is mentioned in the 2000 section as well.

XP uses different Rtenicxp.sys.

I'll try your suggestions.



#4
dencorso

dencorso

    Iuvat plus qui nihil obstat

  • Supervisor
  • 5,970 posts
  • Joined 07-April 07
  • OS:98SE
  • Country: Country Flag

Donator

minf? As in "Minimize INFs"? And where can that be found, please?



#5
MrMateczko

MrMateczko

    Newbie

  • Member
  • 16 posts
  • Joined 29-June 13
  • OS:none specified
  • Country: Country Flag

http://www.msfn.org/...ze-an-inf-file/

actually a jumper's program, how nifty.

 

Even without doing anything to the INF, it dropped from 2kb to about 655kb.

WIth the stuff I've removed, I narrowed it down to about 25kb.

Will test it when I have time.


Edited by MrMateczko, 27 October 2014 - 11:22 AM.


#6
dencorso

dencorso

    Iuvat plus qui nihil obstat

  • Supervisor
  • 5,970 posts
  • Joined 07-April 07
  • OS:98SE
  • Country: Country Flag

Donator

minf? As in "Minimize INFs"? And where can that be found, please?

 

http://www.msfn.org/...ze-an-inf-file/

actually a jumper's program, how nifty.

 

Thanks a lot! :thumbup

 

@jumper: great tool! Thanks for providing it! :thumbup



#7
jumper

jumper

    2014 All-American Masters HJ'er

  • Member
  • PipPipPip
  • 493 posts
  • Joined 21-January 11
  • OS:98SE
  • Country: Country Flag
I hand-optimized both the v2008 and v2014 infs and got them both down to versions that are extremely similiar. Following is my 9x-only version of the v2014 driver inf:
Spoiler

edit: Oops, posted my v2008 inf which is extremely similiar; now it's the v2014 mod with the 8106E entry. :blush:

Edited by jumper, 30 October 2014 - 03:21 AM.

Design feedback requested:
IHAtool - IpHlpApi tester; call various functions and report results
--status-> framework is solid; 22 api's fully supported; preview release coming soon
ComDlg32 wrapper - ComDlgEx meets IpHlpApi wrapper
--status-> PrintDlgExW working in latest SumatraPDF 8^)
Future projects: ImportPatcher40 - dialog interface; Kexter - IP40+Ktree+Kexstubs

#8
MrMateczko

MrMateczko

    Newbie

  • Member
  • 16 posts
  • Joined 29-June 13
  • OS:none specified
  • Country: Country Flag
Sadly, it still doesn't work :(
It hangs on the boot screen the restart after the driver installs.
If i reboot again, I got the same error in ASD.EXE (the windows in the middle) as with the NDIS driver before.
I've used the jumper's inf, as well as the one I shortened myself earlier, still the same thing.
This is really strange, as everything seems to be fine, but things like WINIPCFG.EXE gives an error the the IP configuration is not ready. Obviously no sign of connection whatsoever.
Maybe the 98lite I'm using is the culprit? Maybe use the .SYS file from the 2008 version?
Maybe the fact that I'm running this 98SE from my SanDisk Cruiser Blade 16GB pendrive.
If installing to my real HDD would help? (I really don't want to screw with it, only as a last resort)
Maybe it's because I've installed it with the /p i switch (to force APM instead of ACPI) to install it on a pendrive?
Xe8bIhb.png

Any log files worth sharing?

Edited by MrMateczko, Yesterday, 10:13 AM.


#9
jumper

jumper

    2014 All-American Masters HJ'er

  • Member
  • PipPipPip
  • 493 posts
  • Joined 21-January 11
  • OS:98SE
  • Country: Country Flag
Could be a problem with the driver itself which, despite the 9x entries in the inf, was clearly never successfully tested on Win9x by Realtek themselves.

In the 2014 inf, the 8106E uses the same install as the 8105E in which the only addition over the 8104E is something called EEE which can be enabled/disabled. So lets try creating an 8106E entry in the 2008 inf by cloning the 8104E section:

To the 2008 inf file below
[Realtek]
;8104E
%RTL8104.DeviceDesc%    = RTL8104.ndi,      PCI\VEN_10EC&DEV_8137&REV_03
%RTL8104.DeviceDesc%    = RTL8104.ndi,      PCI\VEN_10EC&DEV_8137&SUBSYS_813710EC&REV_03
add
;8106E
%RTL8106.DeviceDesc%    = RTL8104.ndi,      PCI\VEN_10EC&DEV_8136&REV_07
%RTL8106.DeviceDesc%    = RTL8104.ndi,      PCI\VEN_10EC&DEV_8136&SUBSYS_813610EC&REV_07
And below
[Strings]
RTL8104.DeviceDesc        = "Realtek RTL8104E Family PCI-E Fast Ethernet NIC"
add
RTL8106.DeviceDesc        = "Realtek RTL8106E Family PCI-E Fast Ethernet NIC"
You can also try using RTL8102.ndi as that is DEV_8136&REV_02 compared to the 8106E's DEV_8136&REV_07
Design feedback requested:
IHAtool - IpHlpApi tester; call various functions and report results
--status-> framework is solid; 22 api's fully supported; preview release coming soon
ComDlg32 wrapper - ComDlgEx meets IpHlpApi wrapper
--status-> PrintDlgExW working in latest SumatraPDF 8^)
Future projects: ImportPatcher40 - dialog interface; Kexter - IP40+Ktree+Kexstubs




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users