Search options (Page 2 of 4)

Well...REMing everything but iastor.sys was quite successful. Intel RAID was finally recognized. I'll go on ahead and do a full reinstall tomorrow. Hopefully there will be no issues with the full install. I'm much closer to identifying the conflict now. I just need to get more DVDs.

I previously had this issue and fixed it by REMing out the JAHCI driver. I believe our intel sata issue can be solved in a likewise manner. Being since I currently don't have the time (or DVDs) to test, let me propose this:

REM out all drivers in the [SCSI.LOAD] section ONE BY ONE.

Insert a semicolon ; in front of each driver, test, remove semicolon and repeat on next line.

Example:

[SCSI.Load]
cpqarray = cpqarray.sys,4
;atapi = atapi.sys,4
aha154x = aha154x.sys,4
sparrow = sparrow.sys,4
symc810  = symc810.sys,4
aic78xx  = aic78xx.sys,4
i2omp = i2omp.sys,4
dac960nt = dac960nt.sys,4
ql10wnt = ql10wnt.sys,4
amsint = amsint.sys,4
asc = asc.sys,4

Well then we both agree with the crap part. Otherwise...I was the one to mention 'getting rich', in which I do not mind parting with money to those that make things easier for me. Do you understand that what we have here are equal parts business and personal use. How are you going to charge someone that makes a disc for personal use...for future reference? Are you ready to cater to only those that do distribution? That makes their job easier? That is what I am talking about.
And being that I myself have d/led contributions made by yourself (and I thank you), my main concern were contributions that made software made by others, easier to slipstream. You can't expect to make a program that uses other ppls software to make a profit. Most of us here can do that for ourselves. Either through Integrator, nLite and whathaveyou. Your software makes things EASIER but they don't make things POSSIBLE. I have no qualms about donating to you. Again, I myself use some of your addons. I myself use nLite. But can you see what I am saying?

If you are asking what I contribute, no it is not money. It is my precious time in trying to track bugs...why nothing of Bashrat's recent release works for me. Do I blame him? No. Was I refering to him in my first post on this specific topic? No.
Do I contribute to topic after topic of how this has failed me or how I-am-not-you (inside joke). I blame my motherboard...and maybe nvidia too. I don't know how to code like yourself. I wrote a piece of s&&t (Hey Bash,..this board doesn't support censoring! LMAO) batch that makes renaming easier. I regularly post to the bugtracker.

I need to see you release something w'out bugs. I want you to contribute and be perfect. Then do a funny thing like charge the ppl that helped you out.

PS...I find your contributions priceless (yeah, really). And one of the things I was trying to convey was that the lot of you actually DO do this as a labor of love. So why keep it from the rest by charging...the rest being that use it as  a one time thing.?.?

What is newdev.dll? I'm having a hard time wondering why I don't know the answer.

I don't know what I did in one of my experimental unattends but I got drivers (nvidia specifically) to load but none of my included software show up. I then tried slipstreaming mass storage with previous (batch) dpbase, noted all changes and slipstreamed the rest with 6.06. I know 6.06 removes textmode drivers REGARDLESS so I moved those back to the I386 directory. I used 6.06 presetup, setup.exe...matter of fact I used everything from 6.06. I kept mass storage entries and drivers from previous. Everything seemed to work except after the 2nd reboot (towards the first logon) I get a bsod. I suspect this is nvidia, but then again it's just a guess. I use Acronis backup so I didn't weep like a child last night.

What is newdev.dll by the way? Sometimes it shows up in txtsetup.sif, sometimes it doesn't. Same with dosnet.inf.   I also noticed a peculiar thing about HDA fix. It doesn't act upon i386 if it is detected...granted, but YOUR hda fix works while mine doesn't ALSO HDAPROP.DLL and HDASHCUT.EXE are missing from what 6.06 detects (only dpbase will install these)...I don't know. Can you just force HDA and screw the exist check? <shrug>

I'm trying, but I'm gonna walk away for the time being...my head is pounding...

Don't touch the sticky yet...I'm still tracking raid issues. And I still don't know how the rest of the driver packs are going to behave. Though, if muiz is doing fine, then I don't think I'll have a problem after the raid issue.

Yeah...textmode won't work for me. but in a llttle bit I plan to slipstream old mass storage with old slipstream then use new base to slipstream rest. Need to see where that takes me. lol

Muiz...I really do wonder if it's because we use mce. I'm not sure though. It's the same thing with nvidia and being stuck on v81.98 because of mce.

And there's no way i'm going back to pro. mce is much faster.

Same here...cept with Intel Sata Raid.

Bashrat has released this version not 1 week ago? It will take a while for others to catch up with the nuances of the new slipstream. I believe the post scripts you're counting on are out of date (for the time being). Not only that, but I notice in your post that your script looks for 'DrP'...? It looks for WatchDriverSigningPolicy.exe AND WatchDSP.exe. Also it looks for RogueSpear personal packs. The batch you posted itself is very flawed.

Not for nothing...but this is a pretty new bashrat release and you can't expect things to work out perfectly when it comes to third party batches.
Especially with the release being so recent. With the bugs having not been ironed out yet.

The screen shot is cryptic. Did you ever find out what those missing drivers are?

Are all the devices you mentioned in your post accounted for? Because your screenshot doesn't show.

WOW. Yes on the DPs_fnsh.cmd. Still there.