Search options (Page 70 of 99)

I just noticed something else; I do not find a clue that ATI's ahcix86 is a bus extender, but that is what it currently says.

I thank you for finding these errors.
I had just 7zipped a pack, but will fix them errors you found first.

you could try my gmail.

[V-4] also had this ms_2_exc_skipIfOS error

I asked, are you sure... and you know what?
the link in the FTP itself is not updated.

the older file is gone, but the old link is what I still saw. (an error on Jmicron site)

I pasted its properties into notepad, and changed it to
ftp://driver.jmicron.com.tw/jmb36x/Win2 … .20.03.zip
Et viola, I finally have it.

hi
(much later on) when I looked again, I saw that this "hidden character" was a "tab", so it could hardly have been the reason.

I'll look at this again, and will also look for duplicate filenames.

hi folks
I've tried to make a testpack with support for these laptops using the method ruudboek used, but I may need a file from one of you.

before you look, I must say that the driver at dell has been updated.
CatalogFile = NVDM.CAT
DriverVer   = 04/28/2007, 6.14.11.0119

couple days ago, I read this, got to DELL's driver support, I got R157686.exe and when I uni-extracted it, nvucode.bin appeared to be still cabbed. (file I found was nvucode.bi_)

But, I still got around to edit nv4_go.inf to make it support these HWIDs that were not in there yet, and think it might work. (wanna keep the pack manageble by not adding 57Mb...)
However, the files-list mentions this nvucode.BIN..
I'd like it if one of you could install dell's newest, get that file off, and mail it to me.

if you are adventurous, you can try this file from rapidshare, where the only thing "fishy' is that nvucode.bi_ was simply renamed NVUCODE.BIN.
if you see that nvucode you got when installing the official release is different in size than what I have, then you could make a testpack with the good file and try it.

>>here was obsolete link<<

the edits in nv4_go.inf were more than simply adding HwIDs.. because not all instructions were same, so the sets for each were added.

Hi
indeed, so much for standard..

In this case, Aopen will work on Aopen moboes..
Many months ago I looked into differences in wiring diagrammes of those non-standardised connectors, and then decided I want to use connections that work right away, rather than tinker on those things.
I must still have the notes I made then, but your TS site is good to bookmark.

hi,

are you sure?
http://www.jmicron.com/Driver.htm
That driver on jmicron site ftp is 1.17.18.07

Hi
The current release has those updates in it.
---------------------------------------------------
btw, the error I reported about with M1 is apparently a QSC bug rather than a name-bug.
(when one does NOT use QSC in method 1, it gives an error even when folder is there with correct name.)

Since those Intel chips can be used from single folder, then it will become a single folder in a forseeable future.

Hi
I see the XP driver was updated as well.

if you need these quick, then, for the time being you could un7zip the LAN Driverpack, add the unzipped 2000  files to D\L\M and also replace the files with the fresh XP download.
When you done this, use 7zip to pack the D folder and its INI, and use your updated file
(if you use QSC, then you better first clear that. )

XP/2003=
http://www.marvell.com/drivers/driverDi … &pId=3

2000=
http://www.marvell.com/drivers/driverDi … &pId=2

Erik, do you have an uncabbed copy of nvucode.bi_ in the latest Nvidia drivers?

I extracted files for Dell Lattitude 820, but nvucode.bin_ will not uncab.

The lattitude driver is fairly recent, and when I looked, these models did NOT appear in NV4_go.INF .
CatalogFile = NVDM.CAT
DriverVer   = 04/28/2007, 6.14.11.0119

NVIDIA_G71.DEV_0299.2   = "NVIDIA GeForce Go 7900 GTX "
NVIDIA_G71.DEV_029A.2   = "NVIDIA Quadro FX 2500M "
NVIDIA_G71.DEV_029B.2   = "NVIDIA Quadro FX 1500M "
NVIDIA_G72.DEV_01D7.2   = "NVIDIA Quadro NVS 110M"

NVIDIA_G72.DEV_01D7.3   = "NVIDIA Quadro NVS 110M "
NVIDIA_G72.DEV_01D7.4   = "NVIDIA GeForce Go 7300 "
NVIDIA_G72.DEV_01D7.5   = "NVIDIA GeForce Go 7300  "
NVIDIA_G72.DEV_01D7.6   = "NVIDIA GeForce Go 7300   "
NVIDIA_G72.DEV_01D7.7   = "NVIDIA GeForce Go 7300    "
NVIDIA_G72.DEV_01D7.8   = "NVIDIA GeForce Go 7300     "
NVIDIA_G72.DEV_01D7.9   = "NVIDIA GeForce Go 7300      "

NVIDIA_G72.DEV_01D8.2   = "NVIDIA Quadro NVS 120M"
NVIDxIA_G72.DEV_01D8.3   = "NVIDIA GeForce Go 7400 "
NVIDIA_G72.DEV_01D8.4   = "NVIDIA GeForce Go 7400  "
NVIDIA_G72.DEV_01D8.5   = "NVIDIA GeForce Go 7400   "
NVIDIA_G72.DEV_01D8.6   = "NVIDIA GeForce Go 7400    "
NVIDIA_G72.DEV_01D8.7   = "NVIDIA GeForce Go 7400     "
NVIDIA_G72.DEV_01D8.8   = "NVIDIA GeForce Go 7400      "

NVIDIA_G72.DEV_01DC.2   = "NVIDIA Quadro FX 350M "
NVIDIA_G72.DEV_01DC.3   = "NVIDIA Quadro FX 350M  "
NVIDIA_G72.DEV_01DC.4   = "NVIDIA Quadro FX 350M   "
NVIDIA_G72.DEV_01DC.5   = "NVIDIA Quadro FX 350M    "

yesterday I had a look at nv4_go.inf, then added the stuff these models need, and the only thing that is stopping me from making a TESTpack on NVidia, is that this nvucode.bin file is still cabbed.
(an original nv4_go.inf does NOT have it in the list of "files", but the lattitude's INF does have that.)

Via sata port bus extender gets implemented.

MiniIDE was already implemented.

I contacted available developer to look into this.

about the Five to ten people guesstimate..
You could be right, I dunno.

We don't have a poll option on the board.

We do get reports about BSOD with Silicon Image, and we do want to know which of the drivers causes the conflict(s).
If we disable this one, and get complaints, can I blame you?
------------------------------

Isn't it strange that it picks the wrong driver during txtmode?
I just went through the HWIDS, and found ONE overlapping HWID.
PCI\VEN_1095&DEV_3114&SUBSYS_81361043,

is that the one YOUR machine uses?