1 Reply by Anonim1979

(20 replies, posted in DriverPack Mass Storage)

Looking at:
http://ask.adaptec.com/scripts/adaptec_ … _topview=1
and other asnwers at the bottom of that page

I would say that at least default(?) (there is HTP370 driver in windows?) driver might have *some* problems - at least in RAID mode.
I don't know if the newest Highpoint driver is better.
If I had 1200A card I could test it but as I don't have it - I can't

There are (I googled for it) some pages that speak about successful use of HTP370 drivers but under Linux not Windows.

Go to forum: DriverPack Mass Storage

2 Reply by Anonim1979

(20 replies, posted in DriverPack Mass Storage)

JakeLD wrote:

At least we know AD is causing an issue. I will look into it, for now I suggest you get rid of it if you don't need it of course. I will download the latest driver of both manufacturer and keep the one that fits both. (If possible)

The drivers for HP in pack is the lastest avilable. So no need to look for new.

I have no problem with installing WinXP.
I'm doing ~ once per week - friends/family helper, some outside work  - a few beers are always welcome wink.

I've been using driverpacks for long time - I had much more posts in old forum - now I don't have much free time.


This one PC - it was 15 minutes more work - after BSOD I knew what was wrong since beginning so I moved HDD to standard intel IDE controler (ATA33 max), instaled unnatended windows/ get rid of wong driver (forced update to HPT)/ moved HDD to HPT370 (ATA 100), works done.

GHOSTed C: partition for duration of tests. PC will go one floor down to neighbour tomorrow.

So the problem is not to me but to others with HTP370 who wont know what to do.


So if You or anyone else have some ideas what to put into .ini (no need to make whole pack - I will make it myself) come forth and speak wink

Go to forum: DriverPack Mass Storage

3 Reply by Anonim1979

(20 replies, posted in DriverPack Mass Storage)

With [AD] dir and [AD] ini's entries deleted install is successful.
But that of course is not valid solution.

The PC has to go in ~16 hours. so if anybody has an idea what hwdid need to be added to ini...

Go to forum: DriverPack Mass Storage

4 Reply by Anonim1979

(20 replies, posted in DriverPack Mass Storage)

I did it 4 minutes before - I'm burning CD right now wink
I deleted:
[ad] dir
and [ad] section in ini

Will report in ~10 minutes

Go to forum: DriverPack Mass Storage

5 Reply by Anonim1979

(20 replies, posted in DriverPack Mass Storage)

----

So 810I doesnt work.

Next try- somebody?
As long as I have hardware to test.

Go to forum: DriverPack Mass Storage

6 Reply by Anonim1979

(20 replies, posted in DriverPack Mass Storage)

Debugger wrote:

I did check, all OK...

My bad I checked only AD and H dirs not ini file.

---------------

Still BSOD.
I will check without other packs /cpu / chipset/ etc.


-----

I checked the HDD after BSOD in system on CD with HDD pluged to normal controler
Inside Windows/recovery/system.log

It looks like the driver loaded is:
ahpt3xx.sys  size: 44,998

I supose name change comes from
DriverPack_MassStorage_wnt5_x86-32.ini

[AD]
ms_count=1
ms_1_deviceName="Adaptec ATA RAID 1200A Controller"
ms_1_tag="ahpt3xx"
ms_1_sysFile="hpt3xx.sys"
ms_1_hwids="PCI\VEN_1103&DEV_0004&CC_0104"
ms_1_isBusExtender=false

and as I can see it still loads driver from AD/ dir not h/ dir

Go to forum: DriverPack Mass Storage

7 Reply by Anonim1979

(20 replies, posted in DriverPack Mass Storage)

Reupload .7z file.
You didn't save changes in I!

Go to forum: DriverPack Mass Storage

8 Reply by Anonim1979

(20 replies, posted in DriverPack Mass Storage)

I will try and report as soon as possible - I must make new DVD.

Yes, only one HDD. No RAID 0/1 test possible for now.
I will try to get second spare HDD but no promisses..

Go to forum: DriverPack Mass Storage

9 Topic by Anonim1979

(20 replies, posted in DriverPack Mass Storage)

Abit BX133 RAID with HTP370 installs wrong driver.
tested with BIOS - oldest, newest (HPT 370 RAID BIOS verson 2.0.1024.), unofficial newest hacked with bios for HTP370 2.351

http://www.abit.com.tw/page/en/download … cket%20370

BX133 HWDID Raid:

============
RAID Devices
============
PCI\VEN_1103&DEV_0004&SUBSYS_00011103&REV_04\3&61AAA01&0&98
    Name: Kontroler HPT370 UDMA/ATA100 RAID
    Hardware ID's:
        PCI\VEN_1103&DEV_0004&SUBSYS_00011103&REV_04
        PCI\VEN_1103&DEV_0004&SUBSYS_00011103
        PCI\VEN_1103&DEV_0004&CC_018000
        PCI\VEN_1103&DEV_0004&CC_0180
    Compatible ID's:
        PCI\VEN_1103&DEV_0004&REV_04
        PCI\VEN_1103&DEV_0004
        PCI\VEN_1103&CC_018000
        PCI\VEN_1103&CC_0180
        PCI\VEN_1103
        PCI\CC_018000
        PCI\CC_0180

Tested with DP_MassStorage_wnt5_x86-32_809 but last official version has the same drivers inside.

BST Drivepack installs "Adaptec RCM Device" driver and BSOD on first restart - after TXTsetup.


Masstorage/AD/

; hpt3xx.INF
;
; INF file of Adaptec ATA RAID 1200A Controller for Windows XP
; Copyright (c) 2000 Highpoint Technologies, Inc. All rights reserved
;
[Version]
signature="$Windows NT$"
Class=SCSIAdapter
ClassGUID={4D36E97B-E325-11CE-BFC1-08002BE10318}
Provider=%ADAPTEC%
CatalogFile=hpt3xx.cat
DriverVer=09/18/2002, 1.3

[DestinationDirs]
DefaultDestDir  = 12 ; DIRID_DRIVERS

[ControlFlags]
ExcludeFromSelect = SCSI\ProcessorADAPTEC_RCM_DEVICE______

[Manufacturer]
%Adaptec%=Adaptec

[Adaptec]
%PCI\VEN_1103&DEV_0004&REV_03.DeviceDesc%=hpt3xxPCI,PCI\VEN_1103&DEV_0004&REV_03
%PCI\VEN_1103&DEV_0004&REV_04.DeviceDesc%=hpt3xxPCI,PCI\VEN_1103&DEV_0004&REV_04
%SCSI\ProcessorADAPTEC_RCM_DEVICE______.DeviceDesc% = NODRV,SCSI\ProcessorADAPTEC_RCM_DEVICE______

and driver that should be instaled:

Masstorage/H/

; hpt3xx.INF
;
; INF file of HPT3xx ATA RAID controller for Windows 2000/XP
; Copyright (c) HighPoint Technologies, Inc. All rights reserved
;
[Version]
signature="$Windows NT$"
Class=SCSIAdapter
ClassGUID={4D36E97B-E325-11CE-BFC1-08002BE10318}
Provider=%HIGHPOINT%
CatalogFile= hpt3xx.CAT
DriverVer=01/05/2004, 2.351

[DestinationDirs]
DefaultDestDir  = 12 ; DIRID_DRIVERS

[Manufacturer]
%HIGHPOINT%=HighPoint

[HighPoint]
%HPT3xx.DeviceDesc%=hpt3xxPCI,PCI\VEN_1103&DEV_0004
%HPT3xx.DeviceDesc%=hpt3xxPCI,PCI\VEN_1103&DEV_0005
%HPT3xx.DeviceDesc%=hpt3xxPCI,PCI\VEN_1103&DEV_0006
%HPT3xx.DeviceDesc%=hpt3xxPCI,PCI\VEN_1103&DEV_0005&SUBSYS_100415BD

This driver worked with older BIOSes too.

Go to forum: DriverPack Mass Storage

10 Reply by Anonim1979

(11 replies, posted in Feedback and Support - DriverPacks Base)

Made some more tests.

Beside svcpack.inf problems:

When winnt.sif is in unicode - the output file (winnt.sif) is 0'ed

When DOSNET.INF is in unicode - the output file (dosnet.inf) is 0'ed

When TXTSETUP.SIF is in unicode - the output file (txtsetupa.sif) is 0'ed

It looks like uni2ansi.exe from BASE isn't called in any situation...

PS.
nlite has no problem with svcpack.inf in unicode

-------------
BTW.
One more problem with BTS_base

I have yet to see one instance where
DPsFnshr
called from guirunonce will  finish properly for me.
It in most cases leave D with drivers intact or only partialy deleted
I don't know what breaks it - net 1.1 from svcpack?
first logon as administrator?
It simply quits in the middle of the work.
*Might be the fault of "exit" in one of my cmd* I think - more test....

I think I will try to remove guirunonce call and try to run it manually AFTER 2nd restart right now...

Go to forum: Feedback and Support - DriverPacks Base

11 Reply by Anonim1979

(11 replies, posted in Feedback and Support - DriverPacks Base)

Yes and no.
Tried with a few times FRESH SP2 (so no winnt.sif)
and a few times with my wmp11+hot fixes slightly nlited (but not too much - as nlite breaks WPF/SFC (you will find my post in beta 1.4 nlite forum) so no sfc modification + my trimming source by 0ing unnecesary files not contained in sfcfiles.dll etc etc etc. bell and whistles)

*doesnt't matter*
So it doesn't matter if
- winnt.sif is or isn't pressent
- makecab is newer or older (as in DP BASE)
- expand is newer or older (as in DP BASE)

Also dosnet, txtsetup are modified properly with hdaudio entries

uni2asnsi.exe WORKS if called by hand

It clearly isn't called or is called for bad file
I think it's typo main BS_BASE code
%% insted of %
%2 %1
temp files are mistaken etc.

As I can't see code as I could some time ago when it was .cmd files I can't pinpoit it to single line smile
Send me source and I will look over it if you want.
anonim1979[AT]yahoo.com

PS.
type method is 'dirty' hack wink
type might not be present
also some unicode letters might be changed into illegal characters especially that some strange code page might be set...

Go to forum: Feedback and Support - DriverPacks Base

12 Topic by Anonim1979

(11 replies, posted in Feedback and Support - DriverPacks Base)

(Sorry that not in bugtracker, but it's late and I'm not going to await next 4 hours for one more registration confirmation....)

DPs_BASE_7052
corrupts svcpack.inf when adding entries for audio DP (any A / B / or both) when svcpack.inf cabed in svcpack.in_ is in unicode insted ansi.

My tests ( 2 computers , clean and modifies sources, checked first newer wersions on expand, makecab before finding problem) on XP PRO *PL* (polish) SP2.

The problem is due to bug in calling uni2ansi ( I'm 99,9% sure smile ) from main *.exe file ( uni2ansi.exe itself works OK)
svcpack.in_ is properly expanded, uni2ansi is badly called/or is not called at all, fedit corrupts unicode file, makecab cabs it back...

When svcpack.inf is in ansi  (Polish (and probably other international versions) starts with UNICODE coded file)
by using uni2ansi.exe from DP_BASE or simple trick from DOS:

type file_in_unicode > file_in_ansi

then makecab'ed

DP_base procced it correctly and ads 2 entries with KB888111 and KB921401


BUT when svcpack is in unicode - the output file is 0'ed with only KB888111 KB921401 entries left.

That what corruprted svcpack.inf looks like:

"
??[












KB888111.CAT
KB921401.CAT
"


If I'm not mistaken Fedit doesnt work with unicode?

-------------

BTW.
About Garphic Pack C
As I can't find anymore my post (topis)  on msfn (IIRC) (it was in Graphic Pack C topic) with some of this what is bellow.
About support of riva TNT / TNT 2 /vanta
The last _official_ drivers with support for them were (no matter what is written on nvidia page and readme.txt LIES - send then 2 emails years ago and no change)
66.93_win2kxp_international.exe

with nv4disp2.inf

[NVIDIA.Mfg]
%NVIDIA_NV04.DEV_0020.1% = nv4_TNTxClass,            PCI\VEN_10DE&DEV_0020
%NVIDIA_NV05.DEV_0028.1% = nv4_TNTxClass,            PCI\VEN_10DE&DEV_0028
%NVIDIA_NV05.DEV_002C.1% = nv4_TNTxClass,            PCI\VEN_10DE&DEV_002C
%NVIDIA_NV05.DEV_0029.1% = nv4_TNTxClass,            PCI\VEN_10DE&DEV_0029
%NVIDIA_NV05.DEV_002D.1% = nv4_TNTxClass,            PCI\VEN_10DE&DEV_002D
%NVIDIA_Win2KDualView%   = nvDual,                   DISPLAY\nvWin2kDualView
%NVIDIA_MultiView%       = nvDual,                   DISPLAY\nvMultiView


/......../


; Localizable Strings
NVIDIA                 = "NVIDIA"
NVIDIA_NV04.DEV_0020.1 = "NVIDIA RIVA TNT"
NVIDIA_NV05.DEV_0028.1 = "NVIDIA RIVA TNT2/TNT2 Pro"
NVIDIA_NV05.DEV_002C.1 = "NVIDIA Vanta/Vanta LT"
NVIDIA_NV05.DEV_0029.1 = "NVIDIA RIVA TNT2 Ultra"
NVIDIA_NV05.DEV_002D.1 = "NVIDIA RIVA TNT2 Model 64/Model 64 Pro"
NVIDIA_Win2KDualView   = "NVIDIA Dualview"
NVIDIA_MultiView       = "NVIDIA Multiview"




and in GPC first supported is geforce 256 (7x.xx driver serie I think, probably 71.89_win2kxp_international ?)

[NVIDIA.Mfg]
%NVIDIA_NV10.DEV_0100.1% = nv4,                      PCI\VEN_10DE&DEV_0100
%NVIDIA_NV10.DEV_0101.1% = nv4,                      PCI\VEN_10DE&DEV_0101
%NVIDIA_NV10.DEV_0103.1% = nv4_WSApps,               PCI\VEN_10DE&DEV_0103
%NVIDIA_NV11.DEV_0110.1% = nv4,                      PCI\VEN_10DE&DEV_0110
%NVIDIA_NV11.DEV_0111.1% = nv4,                      PCI\VEN_10DE&DEV_0111
%NVIDIA_NV11.DEV_0113.1% = nv4_WSApps,               PCI\VEN_10DE&DEV_0113
%NVIDIA_CR11.DEV_01A0.1% = nv4_Crush11,              PCI\VEN_10DE&DEV_01A0
%NVIDIA_NV15.DEV_0150.1% = nv4,                      PCI\VEN_10DE&DEV_0150
.....


; Localizable Strings
NVIDIA                 = "NVIDIA"
NVIDIA_NV10.DEV_0100.1 = "NVIDIA GeForce 256"
NVIDIA_NV10.DEV_0101.1 = "NVIDIA GeForce DDR"
NVIDIA_NV10.DEV_0103.1 = "NVIDIA Quadro"
NVIDIA_NV11.DEV_0110.1 = "NVIDIA GeForce2 MX/MX 400"
NVIDIA_NV11.DEV_0111.1 = "NVIDIA GeForce2 MX 100/200"
NVIDIA_NV11.DEV_0113.1 = "NVIDIA Quadro2 MXR/EX"

.....

Go to forum: Feedback and Support - DriverPacks Base