hi
the subversion is not in it, but the drivers are.
I am modifying the mdmhamrw.inf file file.. for smartlink in 3\M\S\1
just had to add
%Modem1%=Modem1,PCI\VEN_1039&DEV_7013&SUBSYS_42011558; clevo DX4EV
Looks like I need not put up a changelog.
You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by Jaak
hi
the subversion is not in it, but the drivers are.
I am modifying the mdmhamrw.inf file file.. for smartlink in 3\M\S\1
just had to add
%Modem1%=Modem1,PCI\VEN_1039&DEV_7013&SUBSYS_42011558; clevo DX4EV
Looks like I need not put up a changelog.
bump
there was another topic, right here, in this forum..
RE >> beta testing
chaz, does the new webcam driver work with older ones?
Hi
It seems I got myself confused.
you want to be part of testing..
Are you able to read this topic?
http://forum.driverpacks.net/viewtopic.php?id=801
I hope so..
Sorry, I thought I read donators automatically saw that testing forum.
Before the opensourcing began, I became beta tester.
I did not immediately find back the topic where I volunteered to do that
I cannot remember for sure, but think I already tested betas before I donated.
Anyhow, I recall I read something about donators being able to see the topic on opensourcing, before it went public, and that was why I thought you'd see the testing forum.
If you are interested in testing betas and nightlies, all you really need to do is volunteer.
Of course, having some hardware what can be formatted anytime is pretty much a neccessity, for live tests will bring out issues that do not surface in virtual PC or VMware virtual environment.
(for simple reason, a Virtual PC emulates hardware known to always work on vanilla windows.)
Kind regards, Jaak
you got into testing, and no longer have ads, don't you..
I was afraid that was gonna happen, set to IDE, drive not detected
Nightly test, triple fail on jmicron... Jeesh, this one is a bear.
muiz, that one on rapidshare, is that same one as in testing forum?
I tested this one earlier this week, and tonight i tested the nightlytest you uploaded an hour ago
both did not go when BIOS has chip set to use AHCI
earlier one worked when Bios was set to RAID...
was doing that test with jmicron set to Raid modus (still with single HDD) just now, and it does not see the drive.
gonna restart, set to IDE.
set to ahci in BIOS, drive not detected (single HDD)
hi
on hindsight, it sure feels like you wanted us to just check wether this was in it or not, and not as much as a request to put it in..
we need to know what you tested on, and your logs
a couple people wasted precious time on things that were already included, and that could set bad blood.
I did not mind much, but have to tell you anyway.
please post a base log (log of the slipstream process), and after you tried setup with the driverpacks integrated DVD, please post the dpsfnshr.log found in windows folder on machine you ran setup on
hi muiz
the subs do not come up with hits in a txt search
I figure that the inf files are all that need to be put in g\A\1 to make this one get detected
otoh, the chipset request was also about file that was already in the packs..
It may very well be that iacob777 does something wrong when he slips driverpacks..
the changelog is in the grafics B nightly topic... where else do I put it?
it is not released yet is it?
but, now we have another guy who can test that nightly.
muiz had that right
g\v\7 has that inf file I see in this download
the nightly worked for the asus barebone I have here.
hehe, barebone?
what a coincidence, I put that up in a graphics b nightly
but, none the less, I will download, to compare.
hi
checked something
;Copyright 1998-2005, Silicon Integrated Systems Corporation
[Version]
Signature="$WINDOWS NT$"
Class=System
ClassGuid={4D36E97D-E325-11CE-BFC1-08002BE10318}
Provider=%Provider%
DriverVer=07/18/2003,7.2.0.1170
CatalogFile=sisagp.cat
this is already included in current release of chipset driverpack.
you tell us it does not work?
hwids match, cat file matches, version of sys file matches
[SIS_AGP]
%SIS.AGP.DeviceDesc%=SISAGP_Install,PCI\VEN_1039&DEV_0001
%SIS.AGP.DeviceDesc2%=SISAGP_Install,PCI\VEN_1039&DEV_0002
%SIS.AGP.DeviceDesc3%=SISAGP_Install,PCI\VEN_1039&DEV_0003
if this does not work when properly slipped into source, you can post a bug report at the bugtracker
link 1, has a corrupt file in it
link 2, files extracted OK
do you guys want me to have a go at it, to include in chipsets for a nightly?
edit, I can have a go at chipsets too, if you want. (before edit, I goofed, said graphics B nightly... hehe)
hi fsfikke
do you know what chipset this motherboard has?
Some mass storage controllers are giving trouble in ne incarnation, and not in other, and some will refuse you access when another mode is chosen in BIOS.. so we'd like to know at least something more about your rig.
The file framedyn.dll, is required for the Windows Management Instrumentation (WMI) processes within windows to operate correctly.
http://support.microsoft.com/kb/319114
I'll be running a couple live setups today, using latest packs, will see wether i have that issue too.
(did not have it four days ago, suspect it won't happen now.)
what operating system do you run on machine you do the slipstraming on?
could you post a base-log?
Name: SRFirstRun
Filename: srclient.dll
Command: rundll32 srclient.dll, CreateFirstRunRp
Description: Created by execution of the Windows XP sr.inf file, which installs the Windows XP System Restore feature, needed for example when installing System Restore into Windows Server 2003. This file should only be found on initial installs/re-installs. It is required for Windows to function on first boot.
File Location: %System%
Startup Type: This startup entry is started automatically from a Run, RunOnce, RunServices, or RunServicesOnce entry in the registry
hi
I pulled the link from older post (where all requests were in one post...)
yep, shows up here, again
note to self, don't load a 64 bit version of vista, 7zip will not work in that,
the x64 version exists, but the one in base, that is probably not gonna work in x64 environment.
(vista, there is a 32 bit environment in x64 versions, I believe, for backward compatibility of course.)
which reminds me I ought to ask what version of vista you run?
unpatched fired up, saw chippin on mforum page
soon as I looged in, it did not show up no more.
so, it is prolly the adsense
now that you mention it, no, not in forum pages
hmmm, patch tuesday happened, several updates got loaded yesterday.
I'll fire up an unpatched machine, see what it shows on that.
Hi
you are testing this in a live machine, and I wonder wether a non OPK'ed version will work
(winPE or OPK)
could you test with a simple source, where you copy your winnt.sif to i386, then run base on it to slip the driverpacks into, and then run setup on that live?
I wonder wether it is a conflict such as some we've seen before
iastor driver could behave like that (there is a long topic about that one..)
seen during setup, and failing to proceed after reboot
If you read that iastor topic, you can read there were strange fenomena when modes of the hard disk were changed, and when orphaned RAID member disks were used.
I cannot help much on OPK,
I wonder why both method one and two are used on a source (I figure you copy folders, to re-use them later)
the thing is, when you first run one method, and then the other method, the first gets undone in more than one place...
hi
just a thing I notice?
You are going to use method 1, on all packs, and that will exceed the path length limit.
Like this, a large number of drivers are not going to work.
DriverPacks.net Forum » Posts by Jaak
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.100 seconds, 6 queries executed ]