Bâshrat the Sneaky

WOOOOOOOOOOOT VERY INTERESTING!!!!!!!! Let's see if I can use this for my DriverPacks... EDIT: Not useable at all for my driverpacks Only usefull for someone who want's to back-up all his drivers into ONE installer and execute it within Windows...

Any clue for what reason it's doing this?

Never heard of that brand before... I'll take a look at it asap... (not today, not tomorrow...)

Hmmm might be handy to someone, but won't be a success story I think...

You can try my DriverPack MassStorage, which you can find in the Device Drivers forum, as overclock said. It includes virtually ALL SATA drivers, so your controller is 99% sure included Bâshrat the Sneaky

ow I misunderstood you.. thought it worked for you... Well anyway, please try my driverpack!

if that works, I'm going to laugh Me too!!! But I can't get anything else out of his post... Now I've read the new posts in the Successful nvraid slipstream topic and what do I see? It's working with the EXACT SAME entries as I'm using!!! If anyone can explain me the difference.... EDIT: @rcordorica: What version of my driverpack are you using? (= what date is in the Read_this.htm file?)

@buletov: No, I DO have them inthere! I think from the first version of my hand! @BigA: good job, but could you PLEASE try my driverpack? I'm using EXACTLY the same entries!

Learn and read from the guide buletov said, as well I did in several other topics, in which you asked the same question as here. (at least three times) Getting your raptor to work hasn't to do ANYTHING with drivers! Remember, drivers are there for hard disk controllers, not for hard disks themselves! Bâshrat the Sneaky

what do you mean by average? first of all, average pc doesn't yet have sata as a default and all the standard (and less standard) sata / raid controlers are inclued in Bâshrat the Sneaky's driver pack, which integrates into your win setup with a few mouse clicks and minor editing of a single file... Can't say it better

@SiMoNsAyS: OK, it MAY work, but if someone gets trouble, I'll blame you Deal? @DisabledTrucker: If I understand you correctly, you're saying that I should move the nvraid entries in the txtsetup.sif file upwards, ABOVE the nvatabus entries in [HardwareIDsDatabase]? @swgreed: thank you

...which is the case in 99% of circumstances The NVRAID controller appears to be an exception, though I'm not 100% convinced of that. I think an email to nVidia is going to be needed to clarify the situation. Well I thought MULTIPLE onboard RAID solutions didn't have this, so... stupid remark of mine Still I'm finding it very odd that this pack still is giving trouble with NVRAID... Why do they have to make it so difficult??? Why can't they make their drivers/hardware in accordance with standards??? P.S.: this discussion is in the wrong topic...

Which Promise controller are you using?

@SiMoNsAyS: huh? this shouldn't work properly! You have to add ALL files to dosnet.inf! At least that's what RyanVM told me, as well as google! @crahak: 7za.exe issue==> I'll fix it. Dosnet.inf info==> I'll make a guide. @rcordorica: yes you posted this before, but it wasn't clear at all.. Investigating it now. Investigated. HOW could I implement this? I don't know!

It depends on the controller you need to be supported...

Please just post it here! Then it can be helpful for anyone searching for it!

ooooh NOW I understand! Thank you! Didn't know that!

Yeah, I know it sounds very ridiculous, but it DID work!!! P.S.: it's CMDOW, not cmdNow..

Ehm there is no 'official' order or anything like that, but you *SHOULD* install them in the logical order! e.g.:-you should install firefox before installing java ==> if prog A requires prog B, first install prog B!

No, unfortunately there is no such variable... As you supposed, you need a batch file to do this: TITLE Setting the %settings% variable CLS @ECHO OFF IF EXIST C:\__SETTINGS__ set SETTINGS=C:\__SETTINGS__ IF EXIST D:\__SETTINGS__ set SETTINGS=D:\__SETTINGS__ IF EXIST E:\__SETTINGS__ set SETTINGS=E:\__SETTINGS__ IF EXIST F:\__SETTINGS__ set SETTINGS=F:\__SETTINGS__ IF EXIST G:\__SETTINGS__ set SETTINGS=G:\__SETTINGS__ IF EXIST H:\__SETTINGS__ set SETTINGS=H:\__SETTINGS__ IF EXIST I:\__SETTINGS__ set SETTINGS=I:\__SETTINGS__ IF EXIST J:\__SETTINGS__ set SETTINGS=J:\__SETTINGS__ IF EXIST K:\__SETTINGS__ set SETTINGS=K:\__SETTINGS__ IF EXIST L:\__SETTINGS__ set SETTINGS=L:\__SETTINGS__ IF EXIST M:\__SETTINGS__ set SETTINGS=M:\__SETTINGS__ IF EXIST N:\__SETTINGS__ set SETTINGS=N:\__SETTINGS__ IF EXIST O:\__SETTINGS__ set SETTINGS=O:\__SETTINGS__ IF EXIST P:\__SETTINGS__ set SETTINGS=P:\__SETTINGS__ IF EXIST Q:\__SETTINGS__ set SETTINGS=Q:\__SETTINGS__ IF EXIST R:\__SETTINGS__ set SETTINGS=R:\__SETTINGS__ IF EXIST S:\__SETTINGS__ set SETTINGS=S:\__SETTINGS__ IF EXIST T:\__SETTINGS__ set SETTINGS=T:\__SETTINGS__ IF EXIST U:\__SETTINGS__ set SETTINGS=U:\__SETTINGS__ IF EXIST V:\__SETTINGS__ set SETTINGS=V:\__SETTINGS__ IF EXIST W:\__SETTINGS__ set SETTINGS=W:\__SETTINGS__ IF EXIST X:\__SETTINGS__ set SETTINGS=X:\__SETTINGS__ IF EXIST Y:\__SETTINGS__ set SETTINGS=Y:\__SETTINGS__ IF EXIST Z:\__SETTINGS__ set SETTINGS=Z:\__SETTINGS_ EXIT In this batch the variable "SETTINGS" is made if there's a folder __SETTINGS__ found in the root of a HDD/CD/DVD.

Had the same problem once... What I did to solve it? Just clean the CD with my T-shirt and it worked! : Hope this works for you too...

[quote name='rcordorica' date='Sep 22 2004, 10:48 AM']update: I added the drivers into the %OEM%\$$\OemDir directory and everything installed perfectly using the method i posted before. No more errors about missing files.[/quote] Good job!!! P.S.: I think I'll use this method in DriverPack MassStorage!

Could you please clarify this? I don't understand what you're saying...

maybe you're right on the RAID part, but it's still required to get Windows on there! (I also think you can only make the raid itself (eg 0/1/5/0+1) AFTER Windows is installed, but you have to install it on one of the disks (JBOD) and use the driver afterwards to be able to use a RAID method) You're half right, half wrong. WindowsXP does have the ability to make a software-based JBOD array with Disk Manager, but I would never recommend you do it. There's also hardware controllers, which have a BIOS of their own which detects the drives when the computer boots. You build an array in that BIOS (before the operating system is even invoked). It's for those hardware controllers that this driver pack is needed. (Anybody find it funny that we're educating the RAID driver guy on how to create RAID arrays? - just giving you a hard time Bashrat ) So summarised it's like this: you can directly install onto a RAID 0/1/5/0+1 setup ONLY WHEN the controller got's a BIOS of his own (= the controller works independantly) Right? (sry people, but I haven't used this kind of stuff before, nor was it asked before...)

What version are you using?