OH, did I tell you that there are days I wanna throw my monkey-wrench in the CRT when I have to work on our congested lower end clients?

XP clients can/will run in virtual machines in corporate low budget hardware. Clients cheap, network bandwidth increased, securised access, higher server CPU utilisation. lower (so they say) TCO and lower fossils burn (or carbondioxide output) because of lean machine with lower risk (but some 'network' congestion can be expected, even with IPV6)

Hi kalmi,
you may not have noticed, but the original topic is OLD, and you replied to something what was solved long ago, and had answers to key words in a question while you forum-searched.

welcome, search and participate have always been better that complain and not search.

I think Jeef writes jsut as a "canary" just like I write jffe when I mean boss.

OverFlow wrote:

I am a hard core individual... (you may have felt some of that energy)

I would not in good concience slipstream a mass storage controler without first slipstreaming the chipset driver that is its foundation... Others may do this and have success with it... not good enough for me. Do it right or Don't do it... chipset must be included and precede mass "anything less would be uncivilized" tongue

First:
I wondered about where we are with "slipstream a mass storage controler together with the chipset driver that is at its foundation".

Hi,
when 2008 started, our tester base seldom had coder insight explained to them.
There were people willing to share effort, and there were real talents doing their thing, and they all had insights and code we had not yet tapped.
I did not write a 2009 "news" post but, had I done that, it would have been about the major change in our fora users.

People writing about a problem were less frequently seen as "complainers" as they were (more than usual, compared to past) often giving insight about a detail we had to look into.
People doing great things decided to add their time, and served their insights and their solutions on a "silver" platter (aka, Ready to Rock.).
Other users stayed mainly just users, but I think they learned a great deal because a LOT more got in public.

I would like to thank many of them for the coding efforts on supported device screener.
(the driver aka INF reader is part of this effort to get ALL screened, so as to find the big buggers.)

I would still like to see a group effort to axepose (diliberate spelling) the driver writer we expise.
YOUR proof of conflict has not been collected for proof of conflict in any of our topics.
When I personally stuck out my neck at brussels MSFT I had my past work, but only mine.
(work in Excel, later excel 2007.. which, by the way, can be augmented by tools offered by Oksana Matveeva from http://mapilab.com/.)

I see home site of mapilabs does not link of the 'excel'lent tools.
the suite of add-ins is at http://www.office-excel.com/excel-addin … undle.html

FAIK, any sort of INF reader had blind spots.
We still need you to find them.

I have a suggestion.

There was a day I allowed JakeLD to take over desktop control of a machine so he could show me some tricks and things.

This can serve all of us? Just follow my thinking? For a camtasia or snagit (or whatever you use), let the tutor run a destop in a VM you are recording from the host.

After that, text and insights.
I know it is more complicated than that, but collaborrative efforts on good tuts will take man-hours, and I remember Erik is (amongst other things) good at tuts.

OH, fwiw, the front room machine vista/win7/other tests has been mucho under-utilised for months.
I won't partake in vista tut. (simple reason, test machine runs dutch or betas.)

BigBrit wrote:

When installing from CD I got the following error:

Access violation at address 004EA1E2 in module DOInstaller_WSED.exe. 'read of address 00000000

Cannot create file "D:\dp\cmdfile". Access is denied.


Worked OK when I copied to a flash drive and ran from there.

Let me know if there is anything I can do to help.

Stu

Hmmm, does this need writable media for temp output?

33

(2 replies, posted in Hardware)

Hi Nykali, welcome to DriverPacks.

I think you can help us save some man-hours (or even only google-time) by providing a link to the driver download page.
We consider it as proper etiquette to do this when you have a REQuest, and we know it absolutely sure helps us help you when you have used DriverPacks and added the REQ and saw conflict. (in which case.. it is more like feedback.)
Either way, a link and more detail on the error saves us time.

Help us help you. You can get amazed.

Hi pclover,

the link you got that wisdom from was written in 2006. (the tell-tale is the version numbers of the packs it is about.)

In my signature, I again link to our somewhat outdated (albeit outdated.. it still has tons of useful insights..) collaboration base tute

I've been scarce, I know that. I should try put time in this tut and should start a new colllaboration effort so as update it, but there're several reasons for my being scarce, so it may not be soon.

(I wish the economic crisis did not bite. It bit.)

And to the point, for third party...

We once had a discussion about doing branded only, and I remember the guy even asked for incomplete line of that brand.
(To his merit, he had built a pack for the models he used, but he still wanted us to fill the gaps he had in there.)
Why was that idea not approved?
Well, third party can be filtered to have as few as possible conflicting drivers only if people use and filter complete driver sets (using known techniques, and reporting/feedback), and since nobody says you cannot build your own strains you may even find out how and where your own built strains conflict with third party "moderated" releases.

hi, before the automated output for supported device listing we had vendor specific devices with rebranded and such detail in those listings, and let me tell you that updating that listing was time-consuming.
In a way, having that rebranded detail could get more google hits, but it made no difference in the number of supported HWIDs.
The publishers do not always care about brand name in the driver, and the automated device list will not find what is not there.

I think we can live with this, because it really took a lot of man-hours to update each page for each release.

37

(85 replies, posted in Vista / 7 DriverPack Chipset)

Midiboy, do you have a link to the driver?

38

(34 replies, posted in News)

Hi,
All of us will have to read the readme in those downloads, and doing that we find out about files not expected in open source downloads.
(there are more than one readme in such type of download, and specifics about non redistributable files are found in many folder.)

Imagine for yourself the better of three worlds.
The read me files found in MDOP (Microsoft Desktop Optimization Pack ).
Those read me files describe deployment and recovery tools and  mention imageX and how you can create installers.
(YOU find out where. OK?)

In XP and Vista, the RTM and OEM (and smal bizz or corp with VLK but no SA.) never had what corporate users paying for SA could buy.
It got better, and will get better still.
The beta of Win7 in public is not same to what "chosen" beta testers test.
There is a public beta for "clean metal", and there is a beta for beta testers for "upgrade" and "crossgrade".
The underground seems to like the ultimate corporate version. The world needs oem, cross, and up, and retail.
(Have you sometimes wondered why vista cracked version is ultimate, and not retail? A retail cannot always do a straight upgrade-like when legacy is not legit-, but it can usuablly be used as upgrade.
(( can it do a downgrade? (°-°) to get legit?))

But.. think? Ey, Large OEM pay less than VLK price. Retail pays a high premium for the freedom it offers you. 8-(

whatever you people may think, I think we are getting shoo'd out of our market.
(and I HOPE they do it, and make it accessible to all..)

Hi,

the tutorial may seem badly out of date because the newer DriverPacks BASE has more functions than what is described in there, but it has a lot of information that never got outdated.
I figure it will be revised with new screenshots, and then we will be able to build newer pages about the functionality we have not yet described in the two forms it now has.
(There is a tut in FAQ in DriverPacks fora, the more elaborate form of same tut (which is, incidentally, also result of collaboration by team members.)  is linked to in that FAQ and people's signatures. And yes, some dudes leeched to ours and used our work in their blog or site.)

When we update the screenshots, we have to apply KIS.
When I or another Main Team get a collaborator doing the write-ups for the new functions we cannot personally test/explain, we can seamlessly enhance what we have and use a few new links with information stored on a MT's private account (What we have used now proved a safe haven).

As a follow up to your very detailed story, the detail of which made my friends correctly answer you, I will add a "remark" about corrupted file error.

Let us suppose you had "file not found, or, file is corrupted" as title of this topic, and you only detail about file name and give no detail on what you did.
Had you done that, some of us would be inclined to ask more detail of you.
Some would get inclined to look at the filenames and run more tests in virtual machine.

Those that feel they have to run more tests to find the error may have been active on the developing side of this, and for "several" reasons  not been able to test ALL variations of what can be done with DriverPacks BASE and DriverPacks.
(I know what that feels like. I know this is the way to burn out.)
You see, there may be versions of OS they did not have a licence to, or had not yet tried in live metal. Or they want to make comparison tests on a operating system service pack they had not yet fully tested all SP variants of, or there is some part of the DriverPacks BASE method they had not tested on all versions of all operating systems.).
Hmmm, I think I just explained how much fun it is to find out wether all permutations were covered while people get to test each new beta and release candidate before we risk a release of DriverPacks BASE and the DriverPacks.

In any case, there are many permutations while testing, and to make this worse than it already is, live metal can have an other result than virtual machine test.

File not found?
In one OS file is found in other OS not, can be a DriverPacks error. But we have also seen that it can be hardware error, and the worst were those few we have seen in server driver files and when it got fixed they kept coming back later on.
(A few of those had to be dropped. We compared ideas about why our hard work got messed up, and realised a few of these server drivers have an inbuilt fixed route to file so "file got mislaid" cannot be worked around.)

File corrupt? We will suggest a memory test and use new brand of media in your burner.

So, let me thank you for the detail, and for not wasting our time.

Hi, could that be because VM has a a Sillicon as default virtual HWID? Or does it not have that?
What is in vanilla?

what's the HWID for that intel SCSI?.
From the top of my head, that must be old, like real 16 bit? or 32bit like UW2?

After wide, you got ultra wide (What I used as well) and  ultra wide 2, and by then I was in the IDE 133 RAID (because IDE drives was a lot cheaper) so I lost the "feel" in real scsi.
hmm. There are two guys in the USA with an old controller and a working scsi drive, and the differnce is that one of those guys still uses the 8 speed scsi burner I threw in as gift. nine years apart, same sort of hardware. Still works.
Small wonder we paid a fortune then.

42

(5 replies, posted in Software)

@ thepandaman.
Helmi asked wether this is a holographic genuine release, and I somehehow doubt you can ever say yes to that.

You got it from a friend.
I therefore doubt you have a legal key to the original OS that may have been the source used to build the disc you need.
Do you have a legal key?
If you have, is it same OS version and OS type?

Slipstreamed versions can be used with key of original key on sticker if current update on hard disk matches original OS type or can be used as update/upgrade to it, which means  OS on hard disk is same, an update lower or equal to SLipstream and not higher than the slipstream, or lower (retail) or there is no OS on hard disk (oem).
(and SP3 will not upgrade/install on gold.)

I think there is a bad burn, and you got to us for help.
(I hope you did not pay for that gift.)

hi?
maybe it moved to IB1?
Maybe it got dropped because it caused a crash with other hardware?

Can you tell us the hardware ID ( PCI\HWID etc) and some detail on the chipset used in that laptop?

look up discombobulator. it is a verb.

answer? Or discombobulator?
a belt wheel on a gear box can exist.
two or more belt wheels can exist on a gear box.

can two belts be on and the motor run?
Yeah.
Can two belts be on and the motor stalls because of friction on the belts?
yeah.

can one win over other?
yeah
does the stronger motor always win in a belt drive mismatch?
(schtum OP uses two drive belts in gear belt wheels of different gear. Or this is test gear with belt wheels added.)
No.

at DriverPacks, we saw that the shorter the string, the stronger it is.
let us suppose each manufactor gets a color.
more detailed string is good, if providers don't keep using each other color for their make.

the shorter string will soon match a search.
the exact string is so much tied to this pinkish vanilla smell with violet overtone and a twang of KiSS that modern search takes two hours on local drives, and eternety on the net.

gear boxes don't work without oil.
Help us help you.

We can try mesh, and if it won't clog the gears we still have to know why it could.
Actually, this is a good analogy.

This one is a weird one?
What happens with one motor on same axle, when you put two belt to the gearbox.

Hi phawxhurst , and welcome to DriverPacks.

Pete Hawkshurst sounds like a BRit name to me.
Pete? Suppose I run a search to all of the downloads we ever had, and I do NOT find the Pci\ven_168c&dev_001a&subsys_2052168c&rev_01\4&1a598d38 you have, then I have wasted almost hundred minutes search on a terabyte drive.

Can you at least please let us get a driver download HINT?
we know we can sometimes make things work, but if it won't mesh, it won"t.

mesh is not a verb. why is is used as?

Hyper V and VM server are different beast?
Far as I know, Hyper-V runs in real x64 metal, or in x64 host, and I thought Hyper-V aware server (metal level) cannot run as full fledged 64 bit aware guest in in X32 host.

faik, x64 VM has to run in X64 Metal OS, as well.
I am not going to buy me 5000 dollar worth of Hardware to again test what I was told/tried over 10 months ago.

I am all ears, tho.
If I am wrong, I am wrong.

Reason for edit, VM X64 guest (-in 64.-)

(extra edit, far as I know, Hyper V in 32 bit is not ever allowed to metal level.)

I get to look at the fora here often, but missed original post before edit.

Hi time I invest into new hardware and nuke it for DriverPack MassStorage and nuke it to newer DriverPacks BASE with DriverPack MassStorage and clean nuke it for newer DriverPack MassStorage.
VM don't make good comparison to live metal, and testing 'our' mettle needs a kettle.

Kurt?
You are one of the people I saw active in the battle for silicon hyll and in other such.

I see you are aware of the ins and outs of DriverPacks, so it is no surprise to see you help us find out about what new DriverPacks BASE with new DriverPacks looks like, in your way of doing things.

Each "module- aka- method" has (or had) its own merit, and its own peculiarities scripts written to each.
Each driver had its own peculiarities written into exceptions, and that sometimes had to be done per method.

I am using had.
I wished I can use had in a true sense, but I know Jeff has seriously tried to (un)separate DriverPacks BASE code from legacy exceptions we have known to be issue if together.

Was I absent?
Did I seemingly leave the scene?
Erm, yep. seemingly.
Was I gone?
NO. And the core of team knew why some of the erstwhile heavies have to adjust.

We all need to adjust to Jeff.
smile

about wisdom
I no longer seem to care what fora part this is in.

We're gonna have to collect wisdom on what we can do (if we had not yet), and what we needn't do, and we are always going to be restricted by non redistributable files.
In our future, MSFT will take care of many things we did for free, and they may do it for free.

The tools MSFT develop(ed) to do this may be scripted to, or may be (made) distributable and (then) scripted to.
(While writing this sentence I saw other possibillites we dream of.)