Search options (Page 83 of 99)

hi
DP LAN 704 should fix this issue
(the L\NV\123 folder and filename error was fixed)

I did not know that muiz, and wondered how it got that way.

Now, at least I know how I got one in that form. In other words, I found the reason.
The current official release has the ini in that name standard, and new base will need it with the un-abbreviated name.
to me, mystery is solved.
still, I missed where the info about the change was posted, and apologise for that error.

(soon as the new releases are up, these few test versions still published on rapidshare are gonna be pulled)

hi
next release will have that in s\r\1

I have a new INI/INF I would like to upload to you, but, no adress

can you hit mine?

in a fresh unpacked UBCD4win I do find a folder where that file is in...
We are testing the DPs_Base bartPE plugin for UBCD4WIN, and that mass storage folder is not used in our tests.

yep, it wasn't smart, and I won't forget it.

They do not all have dual Bios, and once bootblock is bollixed one cannot do a recovery "blind" flash either.
That is ample reason to not lightly advise Flashing, it is still something one should only do when there are serious ducumented issues.

Anyway, tim_st knows about flashing and did some firmware "injection".

has anyone else tested this on "Intel(R) 82915G/GV/910GL Express Chipset Family" and  "Mobile Intel(R) 915GM/GMS,910GML Express Chipset Family" ??

it would have been nice had it worked

hi
can you do us a favour?

can you test this one for us, please?
http://rapidshare.com/files/22957253/DP … nightly.7z
--------------------

-M-M
Update marvell Driver
replaced Ver= 11/14/2006,1.1.0.51 with marvell downloaded from intel 02/09/2007,1.2.0.24
(this version does not conflict with iastor)

[Marvell]
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6101
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6111
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6121
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6122
%mv61xxDesc%=mv61xx_Inst,PCI\VEN_11AB&DEV_6145

-M-M-O
old marvell DriverVer= 01/06/2006,1.0.0.3 Edited out HWID supported by newer version
Enabled for these three
PCI\VEN_11AB&DEV_6120
   PCI\VEN_11AB&DEV_6140
      VEN_11AB&DEV_6141

Massstorage INI update

removed a duplicate entry
[V-3] appeared twice
adjusted drivercount

edit to Highpoint [H-1] (reported by overflow, confirmed jtdoom)
a Fix for win2003, driver does not exist in XP. (also a Bart_PE fix)

Fixed (Muiz)
ATI (Siliconimage) 3112 driver
-\M\S\4 10/23/2006, 1.3.67.0

this is more important to YOU
Test
edit in Mass storage ini makes Silicon Image raid mode drivers load before Silicon Image NON-raid
---------

there are reports that this solved conflicts, which we all suspect is happening, (Bâshrat the Sneaky again mentions it in this topic)
---------
a last note (sorry, I must. We all learn to use search sooner or later.)
>> tut tut, you could have used search, and see posts about silicon, and then you would have seen this test version.

hi
I just did that and put it in  -S\SM\D\4
the reason I did it in a new folder was that the driver SYS files and DLL were different size compared to all the duplicates..

you can do that too
no need for that hotfix file, it is outdated, and replaced with 888111

yep, current public release of mass storage 7.01.1 has an INI, and current release of base7016 actually uses it.
(I had looked at this before I let a mass storage be tested by guys who could do tests on silicon image. And the edit in the INI worked for them.)

most other packs will have an INI too, but not all of them.
I have not seen INI for 3rd partypacks, for instance.
the INI files handle exceptions, so that is why they will make life easier.

you need not be
just edit winnt.sif, set Oempreinstall=0 and make the ISO to test.