You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by Jaak
to jeff and helmi and all experimental minded.
if you are NOT an official win 7 beta tester, don't load (torrents) win 7 from december 18 till fixed beta. (15 jan)
IF you are registered beta tester, you probably also got the news. MVP are often beta testers. I read about a date stamp issue and what I read was not mailed with an NDA delim.
It is beta issue only.
(DriverPacks have a version repository as well, so you know what a date stamp and version check is about.).
MDOP not affected, faik.
Hi,
first of all, a big hooray.
A well meant congratulation to all those having a/final hand in release of latest releases.
To Erik I mentioned we need his knowledge on how things are done publicised in the proper fora, to Jeff I mentioned that open source cannot rely on small team, to myself I vowed I will never again spend 80 percent of available 'free' time to a single project.
We've always stressed that we do not expect you invest in hardware for long term tests.
(And..SOME hard core testers ignored that warning. I personally got bitten for almost 1500 euro on equipment value loss for machines I kept for peculiar tests. Heed thy peers? I now say I will have to heed my own warnings..)
Hi,
I have one long term hard metal machine to test mettle to kettle.
(doesn't sound like me?)
Hi, I tested DriverPack MassStorage 901 with 901.3 and had a conflict on this type MOTHERBOARD and had this (fully described to detail we need.).
That has always had more weight than "I tested that in VM."
Where do I stand now? (jan 2009)
In practice? Far behind any sysprep guru, because I seldom if ever get to do (even smallish) roll-outs.
In theory? I leave development to the guru. Yet test their and my theory against real metal.
The kettle drumm makes a rolling sound, and is our soul.
I sing a song of discomfort when I feel blue.
These days, with the things people in the teams here do, I saw team have new bloodlines well established and mingled with old.
To that, I say welcome to DriverPacks 2009, and I also say that you guys KNEW november 2007 was but key to the changeover year.
IF november was great, what about 2008. I said that, and we get the answer.
2008 was benign.
2011 is going to be easy.
MDOP won't probably fully make it to mass. (full MDOP is only available to soft assurance and premium msdn.)
Hey? Maybe DriverPacks won't be needed. .bleh.
do you think I (or anybody in his right mind.) would show you a link to a torrent with a copy of an original CD?
jaak i didnt get enything in what u sayed man
that is quite common.
basic steps?
make a full copy of the source CD (an original)
If this was a XP RTM (also known as.. first release, gold, in other words.. XP without any SP..) then you can slipstream it to SP3 with two steps because SP3 will NOT do the update to RTM.
(in order to slip SP3 to gold, you stream SP2 for IT professionals to it first, then slip SP3.)
For the other guys. It can be handy to have three SP versions of a gold source CD.
You shall not have a XP gold do repair on a sytem installed with XP gold if that system has had updated itself to a newer SP.
In the same vein;
A SP1 source installed machine can be repaired with either SP1, SP2, SP3, which depends on the SP status the XP had updated itself to, when the repair is needed.
More Info, for PROS and noobs..
If you don't know how to figure out what update status a machine had (and because of data; format is OUT of the question.), then hook up its hard drive up to another machine and look for *SP*.* to find the cabs on hard disk (with show hidden/system/show extention ON)
It is very difficult to find out what OS version was originally installed. The Sticker on the box can help.
slip SP3 to the clean source before you do Method 1, txtmode only.
Here is an easier version of the instructions...
Use a repair disk that Does Not have DriverPacks added and you will not have this issue.
DriverPacks does not currently support attended installations (like a repair)
- If you can follow instructions like the ones posted above, it is possable.
- (it is still not supported... but it will work)Hint:
There is only one way that you can do a repair with an unmodified DriverPacks slipstreamed disc...
IF the only pack you selected for your slipstream was the Mass Storage Textmode checkbox.
Hi,
the HINT Overflow put in his answer will work.
The keyword is TXTMODE ONLY.
Use DriverPacks BASE with only DriverPack MassStorage, and select mass storage, txtmode only.
I think you may find it works when you used METHOD 1. (That is the only refinement to the hint I can offer.)
outbreaker, a HWID in a VM is bull sh*t to us
A blue screen in a VM means a flawed INI, or a flawed source DriverPacks was run to.
we have to know what you did.
all the steps in how you built the install media.
what you ran when you ran DriverPacks BASE.
and what you ran that installer in (hwid)
I can run a DOS.5.0 with win 95 in a VM and run XP upgrade from it.
see? we need to know.
20 hours real work better than hwid laundromat, for brand cognizance, and not a lot of hapennies per baker's dozen.
3 seconds job is better than 20 non paid hours, and no throppence for the man.
Jeff, You know we can live with 3 seconds, barely anybody was able to spend the hours ONTO the hours, ONTO the hours.
That, Jeff, is the best thing happened to DriverPacks.
(and, the driver team can release.. with little main team oversight.. not a ten hour hoopla per release..)
happy 2009.
Whoopla, the word stat has no cognitive to any brand, and brand relevancy was automagicaly thrown away in an INF reader.
The automated device reader for HWIDS has a few holes, and driver vendors have no respect for brands.. and an INF will never show a brand what was not properly written in the oem branding at bottom in INF to start with (and its top comments are often bullsht too).
A hwid. It will have to be run in the basic metal. That is what we need.
What you did, ??, to me that is the puzzle.
For definitive live tests, use real metal.
For experiments, first use a VM in a non critical machine, then use a non critical real metal machine and go live to real metal.
((live tests, easy... swap out real hard disks)).
STAT = such thing as this?
happy 2009.
jt
I had to do edits to my own latest posts..
I have to cover my ass.
I don't want to do flames and my grammar is often not grammar, and my truly meant apology was.
I won't have to apologise to DriverPacks for things I helped DriverPacks do for XP.
I can not help in vista or future OS until the time we have what we need have.
Jaak.
I will apologise to shahed.
I said I did not know shahed from DriverPacks.
What the hurmphh..
I should know when I have to ask I have all I ever stood for here get pullled, or that I have to ask DriverPacks support for vista and XP get two separate sites.
I see XP/2003/2000/2000 as separate entity. (because the tool used is seen as not fought by msft.)
I see a tool based on SA subscribtion will limit the use to those with SA.
(S. A. aka software assurance.. a form of subscribtion)
As is, (to my regret) the old Free DPint.exe, the old waik, the old WIM, is not free and is not comparable to the best of tools we have for free.
(for vista and 08 and 07; dpam, and winpre/winpe is a powerful module in dpam. WIM builder for vista and 08 or win7, and downwards, are in the dpam tool).
Licensed beta testers may have seen this evolve, and may have helped resolve issues it had with early OS in this NOT yet liberated manager.
For now, it is not yet liberated and not intended to be a vehicle for setup in any form I know of.
Hence forth, my word;
caveat.
Hi Outbreaker,
it must have been over 17 months I last looked at virtual box (the product I think you mean that was once called that way).
Many here have MSFT VPC 2007 (always free) or VMware (free is Limited.. or a trial, or a paid).
(I have a legal platinum VM workstation and server from VMware).
So, to me, a secure VB like sandboxie in PC2007 is a VB in a VB.
It amazes me that mass INI fails in a VB (and I mean in A..) like in a within A VB in A..VB.
If it works in another parent/daugther VB, tell us.
Just tell us how deep the VB is in sandbox.
FWIW, I used to test the mettle to the kettle.
These days, I have to few kettle.
I prefer to see, and many here are like I, hard metal live tests.
In extremis, drivers have to drive metal.
Three wishes.
For every thought thought, a thought we not miss and not reply to.
Do what we can, to not have to msft do what we can.
Do your worst, and do your best think within contraints of existing rules, and stay within.
Janus to Febris, "is it getting cold out here?"
Nah..
Thor iced Eaneas's socks. Eneas was just not used to keeping his socks dry.
He got them wet after his dip?
Nah.. Aeneas got in the kilu kivu for an hour and found his socks in the snow.
Febris, Thor was never out the sauna? How could he?
What's the do with females about socks?
Caveat venditor.
- - - - - - - - - - -
In an earlier post I mentioned, litterally, 'Caveat' and only that.
I meant "beware.
Let us not forget the meaning of caveat lector (all reader beware), or caveat emptor (all buyer beware).
Caveat venditor means seller should look at something he ought to be aware of.
(Caveat venditor)
Caveat venditor is Latin for "let the seller beware".
It is a counter to caveat emptor, and suggests that sellers too can be deceived in a market transaction.
This forces the seller to take responsibility for the product, and discourages sellers from selling products of unreasonable quality.
The only thing DriverPacks have to abide to is that methods (what you can do in there) and tools (what is provided by open source) used to get our users a true DriverPacks open source, does not use a patented tool we have no licence for.
MY three wishes.
* For every thought thought, a thought we do not miss.
* Do what we can, to not have to 'msft' do what we can.
* Do your worst, and do your best think within contraints of existing rules, and stay within.
call it So Fine
I most certainly hope HDMI drivers don't become like another soundmax-version-nightmare
I asked OverFlow he look at your user status, and I hope he will give you access to testing team.
You will find there is a steep learning curve, and a lot of reading to do.
(the more interesting posts are about dissemination of files like dosnet.inf and txtsetup.sif.. and those are from over two years ago.)
Hi,
Helmi speaks German.
You know, i like you.
Long time ago (in 1977, if you must know), i wrote my first attempt in English and had my friend look at it.
I had not had English at School, and used lower case i in the middle of sentence.
Had I not been told then, I would still use i when I should use I for i.
I also wrote in a poor grammatical style back then, and still do.
I blame that on my Flemishness.
English by ear. You do fine.
In writing, not quite, because ear and ere sound the same to the ear here.
Back then, in 77, I decided to learn the basics. I got to a library and got me longmans simplified English novels.
I used a dictionary, and paid attention to spelling. I never much mastered advanced English grammar, but, hey, I can play by ear.
What I am saying, sir, is that you can learn and you shall not be embarrassed when you ask to have fine points explained you.
hi,
it can stay black because of memory timing issues.
This can be triggered when chipset drivers load and enhanced speeds "suddenly" do not match what ram can (or cannot) handle.
(I have seen things like this happen, NO bluescreen.. at cold boot one sees BIOS.. in windows Pnp, blackness.. changed RAM to other brand with different timings and windows loaded just fine.)
Hi predator2003,
first off, welcome. I recieved email.
I wanted to look up what you had posted in the past, and see you are coming from the woodwork out, which is pretty much what we ask our users should do so you can help us help you.
How do we check wether signing is broken?
First.. How do we know that a driver is MSFT WHQL signed? The vendor download site either claims it is, or it doesn't.
The INF has txt in it, and that "may" give you an idea, but most often won't.
(besides that, when you edit the INF, signing can break.)
There IS a way to see wether original download was signed by MSFT..
Rightclick the driver.CAT file, click tab for properties.
Then click the tab for digital signature.
If you see microsoft in there, it was submitted to the quality labs and got an approval.
(Which unfortunately... Which doesn't mean it will happily work alongside its older kin and variants.)
I personally think that the signed driver got tested on the hardware it had to work on, and does not crash with the supplied hardware.
However, we have been telling the world (and I am trying to tell MSFT) that OEM driver writers have created an impossible situation which is of interest to EVERYBODY doing roll-outs on different machines.
(Hey, not always "wildly" different. Example. A few weeks ago I saw an Nvidia driver for a Geforce 6600 would not correctly work on a different brand Geforce 6600.)
We hope to not have to break signing when we have to work around issues, and tell people they can edit DriverPacks (or even create their own private build) to fill their own need.
by the way, your English might be easier on people than mine. 
Hi, DriverPacks BASE PE plugin is not method 1/not method 2, it is PE plug-in.
DriverPacks have mass PE plug-in (was not easy.. each update to DriverPack MassStorage will apparently result in some unhappines), and DriverPacks teams are working toward lan PE plugin. (not easy. Lan can cause blue screen.)
To make life truly miserable, Mass, Lan, chipset have to tapdance to same version of a tune, in same step (chipset wise/driver wise/OS wise).
ERD, far as I see, has a typical Microsoft problem when you use it to repair.
Version incompatibility (in service packs of same OS.)
I could call it Atonality.
And they have, far as I know, NO tune-fork to work around it in ERD.
(thank god M$ have released some 'across OS SP version' solutions for the backup utility. That tool allows you to get backup data back from another partition or HDD.. Before that tool, better NOT set up to same hard disk, and use exact same SP, hope backup imported without account warnings.)
I know UBCD4Win has a great set of tools.
One might think the build you build is compromised.
I don't know much about this new form of ERD, and frankly, if you have to alter ERD, you might think that build is also compromised.
You could get helix forensic tools. But hey, that's not from MSFT, so ...
(a form of ERD exists since windows 95.. I used it a LOT in 95. The version of ERD was the version you found on the install CD. and, yes, 95-sp1 ERD did not work on 95-OSR2)
Hey YOU.
you do have the balls.
My goal is to be able to have many up to date virtual machines with various operating systems (Xp home, xp pro, vista 32, vista 64, etc). When I build a new PC, I PXE boot linux, mount the relevant VM disk as a network block device, and dd the partition to the new hard disk. I then reboot and PXE boot LiveXP, run OfflineSysPrep to inject mass storage drivers. Finally, I reboot into windows and run DP_Install_Tool. So far I have everything working except the DP_Install_Tool.
One thing jumping out (what I read, and I do not claim to fully understand.) is off line sys-prep, a non-disc based iso off line, and then a path/signing issue.
I don't have the hardware to run that sort of setup.
I think you will get a few helpful hints by other people.
We do have a sub forum called universal imaging.
---
and I still think you have the balls to test testpacks, so why fish?
I left an angelworm.
Fredric Brown must love me.
Placet is a lonely planet is the best.. no, angelworm was.
I was actually rewriting txt above because .. well because.
(there are a few meaningful edits by now.)
The txt you see last is not the txt you saw last is one of the things I wish was not possible here...
But.. Trust us.
I (acting for my self.) will tell people when I did an inline txt change that could change the 'flow' of a topic.
The moderators here are fair people, and they know they often have to re-read changelogs when stepping 26 gets anounced in a testing topic, then skip to 115 post about step 26.
(I know that reading up on older stuff is often a bore, and MORE often a rethink experience.. or whatever.)
whatever you read in post 3.
I got mad about the situation. I stuck out my neck and hope to truly escalate/expose shoddy, disconformal -conflicting- vendors to people with influence.
I don't like what I wrote there.
My ignorance about tru grammar, what I wanna say is not easy either, and my Flemishness has a put few quircks in that txt.
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.077 seconds, 7 queries executed ]
