Search options (Page 6 of 99)

get to end up with all HDD and opticals before card readers; yes.

We all learn by example, don't we?

I was virtually unable to pour in the time required to keep up with things main team can do after I got back to work after surgery.. This was because I have had to spent the better part of my free time on chores and tasks I have to fulfil, all of which were triggered by a house remodelling I have in advanced planning stage.
I also have the sudden discomfort of having over 11,000 items that were in storage coming in because the storage space I had them at cannot store them any longer. (The space I rented as storage is now in an inheritance and has to be freed.)

anyway, it seemed somewhat odd to see a main team (roguespear) do releases and not have access to the topic where it is done, or the ftp we keep them.

I won't have the time, tho.
I suppose twig123 will be asked to update.

as for tuts, jeesh.
Erik, fire away, WE ALL need the tut you just mentioned.
And, we should help rewrite the tut on base AFTER Jeff finds no more new features and improvements he wants added.
SAD and PE building module is becoming of age, sysprep module is in a pipeline, M3 (which is, perhaps, for getting 32bit baseline OS to HDD, and M3 does the archived DriverPacks.)
((we established that M1 and M2 installs run for roughly same time, and M1 has a couple advantages.. so M3 could be the answer for the things that cannot be done in M2 without the build time required for a full M1))

@ Ra
about REQ

I suggest YOU start a REQ or (why not?) help build a new REL.

Hi,
I edited the earlier comment (it sounded somewhat gruff, and probably came over in a manner I did not intend.)

The essential thing was said in there, tho.
A tinkered CAT is of no benefit to us tinkerers.

hi abdou

I suspect there is (a quite common problem, actually) a missing modem sound driver preventing proper install of sound.

IF your modem driver is not in Third Party DriverPacks please REQ the modem driver in 3rd party forum.
We appreciate the thoroughness of a post like this one, though.

thank you very much for the links and details.

hi
actually, DriverPack MassStorage does not list PCI\VEN_8086&DEV_266F at all.

oops

legacy will be a thorn in our sides.
I wish people stopped screaming about adding REQ for ancient hardware, and I also wish WHQL would have a good screening against old and ancients with NO 'my cards only" restriction.

scrap gut
fdisk will not recognise more than four primary
oops, did you have more than foure drive letters?
--------------------------

listen
fdiks cmbr /2 can throw an error (1876 or something like it.. my memory is poor)

go to dos, and do fdisk /cmbr 2

Warning
whatever was on HDD2 and had same erroneously designated letter may now be missing

advice
never change boot records and extended partition table if you cannot afford to lose data

what to do if data is not to be lost.
remove / disconect all; bring in a spare

now the fun part, helix, ubcd4win and other off line
do you realise that a faulty mobo (controller or south bridge) can have you go thru all what I went thru, and what you did?

that a north bridge is a lot easier to find fault in?

Oh frigging no, time zone is not the same as "twilight zone"
I AM ashamed about the fact that I cannot link to the skipping "broadcom" drivers
(Is this because the broadcom generic chip is used by a wide variety of 'OEM-whom-uses-broadcom"?)
I remember I scanned every single of those  OEM "broadcom" with utilityscanner, and it outputted an empty csv.

for what it is worth.
somebody should link to \old DriverPacks
collect those over a year old

in Wlan we had like almost 300 folders
DIR /S | yopie001.txt
dragdrop (this is a cmd tool available to interested, team and testers with access to test dowwloads)
exell2007,
sort
root folder tally

This DriverPacks BASE release candidate has a helluvalot of revolutionary changes.
In essence, SAD is becoming some sort of M3.

When one is not using all of the features this RC has, then one can quite easily miss unknown bugs while the beta is in testing, and that is where our call for a "drive testing" by the large public is needed.
Some of the new features will most probably become big hits, and some improvements in the way things get processed are probably not going to be noticed.

Jeff has listed MORE changes than I was capable of testing.
Others tested those.
We can use your help, and this is a good opportunity.

what do we expect to hear from you when you report?
what did you do?
what did you expect our programme would do. (what was the result you expected/and the result you got?)
Can you reproduce it?
Do you know the fix?

There is better error checking code in DriverPacks BASE than ever before.
Nothing in this world is perfect, and one of the saddest things is that some drivers are themselves causing us quite a bit of grief.
DriverPacks BASE is backward compatible with older DriverPacks, tho.
Driver conflict related problems can have a relevancy to error checking in DriverPacks BASE, but they are most likely to be handled in the driver forae.

There is a lot of work being done on support for PE/ubcd4win.
It looks like ALL future main DriverPacks will have an INI, but do not despair when you have one that has no INI.