Topic: [NEEDS REPLY] 0x7B BSOD w/ JMicron JMB363 SATA RAID

Hi,

I'm new on this forum and new in integrating updates and driverpacks.
I have a Win XP Pro NL SP2 (dutch language), and wanted to create a bootable CD
with september updatepack and framework addon from Ryan VM.
I use a sata2 HD as boot HD, JMicron JMB36x, Ali M5229, Ali M1567 on the mobo.
Because I don't have a floppy drive, I decided to integrate the driverpacks on this nice website.
The integrating went fine. But when I try to install XP Pro when the install reboots my pc,
on the windows xp boot screen, I get a BSOD.

What I did : Copied all the files of my XP Pro SP2 NL CD to a HD, used RVM integrator 1.4.2,
with advanced set to convert Unicode to ANSI (I read this is needed for a dutch version of XP),
to slipstream the dutch september_updatepack and the dutch framework_addon.
This went fine no problems.
Than I used the latest Driverpack base and driverpacks for CPU, CHIPSET, MASS storage, LAN and WLAN.
Integration went fine.
Burned with Nero, bootable CD with BOOTXP.IMA
Tried to use the bootable CD.
CD booted fine, install copied some files, recognized my sata2 HD (yes!), setup continued install with copying files,
everything ok, after all the copying, the setup needed to reboot the pc. Reboot, for a second I see
the windows xp screen... than BSOD 0x0000007B, 0xF79F7528

Mmm, I think that I did everything in the correct order.

I already tried different setting for the DP base, none worked that I tried.
I probably do something wrong. Can someone help me?

Here are the ini files, and the log

2006-10-02 23:26:50 : <INIT> DriverPacks BASE 6.09 initialized.
2006-10-02 23:26:50 : <INIT> Host environment: WIN_XP Service Pack 2 on X86 CPU.
2006-10-02 23:26:50 : <INIT> Imported proxy settings from Internet Explorer.
2006-10-02 23:26:50 : <INIT> Start scanning for DriverPacks for the wnt5_x86-32 platform.
2006-10-02 23:26:50 : <INIT> 	Detected DriverPack Chipset 6.09.1!
2006-10-02 23:26:50 : <INIT> 	Detected DriverPack CPU 6.09.1!
2006-10-02 23:26:50 : <INIT> 	Detected DriverPack LAN 6.08.1!
2006-10-02 23:26:50 : <INIT> 	Detected DriverPack MassStorage 6.08!
2006-10-02 23:26:50 : <INIT> 	Detected DriverPack WLAN 6.08!
2006-10-02 23:26:50 : <INIT> 	Could not detect any 3rd party DriverPacks.
2006-10-02 23:26:50 : <INIT> 	Finished scanning.
2006-10-02 23:26:50 : <INIT> Detected settings file "G:\driverpack base\DPs_BASE.ini".
2006-10-02 23:26:50 : <INIT> Windows XP Professional -  SP2 detected.
2006-10-02 23:26:50 : <INIT> The platform wnt5_x86-32_disc will be used (which is the 'disc' installation platform for the OS family 'wnt5_x86-32').
2006-10-02 23:26:50 : <INIT> Imported settings from settings file.
2006-10-02 23:26:50 : <INIT> QuickStream Cache directory not found!
2006-10-02 23:26:50 : <GUI>  Initialized GUI.
2006-10-02 23:26:50 : <GUI>  Created a list of all available language files.
2006-10-02 23:26:51 : <GUI>  Set the last used language, Dutch, as the GUI language.
2006-10-02 23:27:18 : <GUI>  Changed Windows installation files OR export (depending on the installation platform) location to L:\XP\CD-ROOT.
2006-10-02 23:27:18 : <GUI>  Windows XP Professional -  SP2 detected.
2006-10-02 23:27:18 : <GUI>  The platform wnt5_x86-32_disc will be used (which is the 'disc' installation platform for the OS family 'wnt5_x86-32').
2006-10-02 23:29:25 : <GUI>  Exported settings to G:\driverpack base\mijnsettings.ini.
2006-10-02 23:29:33 : <GUI>  Refreshed UpdateChecker with success.
2006-10-02 23:29:40 : <GUI>  Saved settings!
2006-10-02 23:29:41 : <GUI>  Closed GUI.
2006-10-02 23:29:41 : <SEL>  Selected module: mod_slip_wxp_x86-32_disc_m2.
2006-10-02 23:29:42 : <PREP> Removed all attributes from \I386.
2006-10-02 23:29:42 : <PREP> Generated \I386\winnt.sif file.
2006-10-02 23:29:42 : <PREP> Created a backup of \I386\txtsetup.sif.
2006-10-02 23:29:42 : <PREP> Created a backup of \I386\dosnet.inf.
2006-10-02 23:29:42 : <PREP> Created temporary working directory.
2006-10-02 23:29:42 : <SLIP> Created necessary directory structure for method 2.
2006-10-02 23:29:42 : <SLIP> Copied files necessary for method 2.
2006-10-02 23:29:44 : <SLIP> Extracted files necessary for method 2.
2006-10-02 23:29:46 : <SLIP> Created \I386\presetup.cmd file.
2006-10-02 23:29:46 : <SLIP> Updated \I386\txtsetup.sif to support method 2.
2006-10-02 23:29:46 : <SLIP> Updated \I386\dosnet.inf to support method 2.
2006-10-02 23:29:49 : <SLIP> Copied DriverPacks to \OEM.
2006-10-02 23:29:49 : <SLIP> Created QSC directory.
2006-10-02 23:29:51 : <SLIP> Extracted DriverPack MassStorage to a temporary working directory.
2006-10-02 23:30:12 : <SLIP> Created QuickStream Cache for DriverPack MassStorage text mode drivers.
2006-10-02 23:30:12 : <SLIP> Slipstreamed DP MassStorage text mode drivers using QuickStream Cache.
2006-10-02 23:30:22 : <SLIP> Removed entries from \I386\txtsetup.sif that will be updated.
2006-10-02 23:30:23 : <SLIP> Removed entries from \I386\dosnet.inf that will be updated.
2006-10-02 23:31:22 : <SLIP> Updated \I386\dosnet.inf and \I386\txtsetup.sif to support DP MassStorage text mode drivers.
2006-10-02 23:31:22 : <SLIP> Updated \I386\winnt.sif to support method 2.
2006-10-02 23:31:22 : <SLIP> Updated DPsFnshr.ini to disable KTD.
2006-10-02 23:31:22 : <SLIP> Updated \I386\winnt.sif's GUIRunOnce section.
2006-10-02 23:31:22 : <SLIP> Slipstream finished in 1 minutes and 42 seconds.
2006-10-02 23:31:28 : <CLNP> Temporary working directory successfully deleted.
2006-10-02 23:31:28 : Program terminated.
[General]
; preferred language
prefLang	= "Dutch"
; yes/no, enable or disable the wizard-style buttons, if not specified: yes
wizardButtons	= "yes"
; yes/no, enable or disable the GUI, if not specified: yes
GUI		= "yes"


[Settings]
; disc/bartpe/multibootDisc
instPlatform	= "disc"
; trailing backslash is allowed, but not necessary
location	= "L:\XP\CD-ROOT"
; none/all/select, if select, specify them below, if not specified: all
DriverPacks	= "select"
; 1/2, method to install the DriverPacks, if not specified: 2
DPsMethod	= "2"
; GUIRunOnce/RunOnceEx/custom, if not specified: GUIRunOnce
finisherMethod	= "GUIRunOnce"


; this section is optional!
[OptionalSettings]
; none/all/select/paths/patterns, enable or disable Keep The Drivers (KTD) , if not specified: none
KTD		= "none"
; yes/no, enable or disable QuickStream Cache (QSC), if not specified: yes
QSC		= "yes"


; you should only add this section if you've set [Settings]\DriverPacks to "select"
[SelectDriverPacks]
DP_Chipset	= "yes"
DP_CPU		= "yes"
DP_LAN		= "yes"
DP_MassStorage	= "yes"
DP_WLAN		= "yes"
DP_MassStorage_textmode = "yes"


; this section is optional!
[OptionalSettingsOther]
; CCC/CCP, use ATI Catalyst Control Center or ATI Catalyst Control Panel (only relevant when slipstreaming DriverPack Graphics A)
ATI_cpl		= "CCC"

I can not give the finisher ini as I got the BSOD.

Thanks in advance for any help!

ninouchka

Last edited by ninouchka (2006-10-03 19:25:21)

Re: [NEEDS REPLY] 0x7B BSOD w/ JMicron JMB363 SATA RAID

Maybe its better to post your HWID's


And you better use codetags on your posts wink

http://www.driverpacks.net/Downloads/save_hwids.exe

Last edited by muiz3 (2006-10-03 17:33:50)

Re: [NEEDS REPLY] 0x7B BSOD w/ JMicron JMB363 SATA RAID

here are my HWIDs

 

=========== 
PCI devices 
=========== 
 
 
PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&267A616A&0&C0: PCI standard host CPU bridge
PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&267A616A&0&C1: PCI standard host CPU bridge
PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&267A616A&0&C2: PCI standard host CPU bridge
PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&267A616A&0&C3: PCI standard host CPU bridge
PCI\VEN_10B9&DEV_1563&SUBSYS_00000000&REV_70\3&267A616A&0&38: PCI standard ISA bridge
PCI\VEN_10B9&DEV_1689&SUBSYS_00000000&REV_00\3&267A616A&0&20: PCI standard host CPU bridge
PCI\VEN_10B9&DEV_1695&SUBSYS_00000000&REV_00\3&267A616A&0&00: PCI standard host CPU bridge
PCI\VEN_10B9&DEV_5229&SUBSYS_52291849&REV_C7\3&267A616A&0&90: ALi M5229 PCI Bus Master IDE Controller
PCI\VEN_10B9&DEV_5237&SUBSYS_52371849&REV_03\3&267A616A&0&98: ALi PCI to USB Open Host Controller
PCI\VEN_10B9&DEV_5237&SUBSYS_52371849&REV_03\3&267A616A&0&99: ALi PCI to USB Open Host Controller
PCI\VEN_10B9&DEV_5237&SUBSYS_52371849&REV_03\3&267A616A&0&9A: ALi PCI to USB Open Host Controller
PCI\VEN_10B9&DEV_5239&SUBSYS_52391849&REV_01\3&267A616A&0&9B: Standard Enhanced PCI to USB Host Controller
PCI\VEN_10B9&DEV_5246&SUBSYS_00000000&REV_00\3&267A616A&0&28: ULi AGP v3.0 Controller
PCI\VEN_10B9&DEV_5249&SUBSYS_00000000&REV_00\3&267A616A&0&30: PCI standard PCI-to-PCI bridge
PCI\VEN_10B9&DEV_524B&SUBSYS_00000000&REV_00\3&267A616A&0&08: PCI standard PCI-to-PCI bridge
PCI\VEN_10B9&DEV_524C&SUBSYS_00000000&REV_00\3&267A616A&0&10: PCI standard PCI-to-PCI bridge
PCI\VEN_10B9&DEV_524D&SUBSYS_00000000&REV_00\3&267A616A&0&18: PCI standard PCI-to-PCI bridge
PCI\VEN_10B9&DEV_5263&SUBSYS_52631849&REV_40\3&267A616A&0&88: ULi PCI Fast Ethernet Controller
PCI\VEN_10B9&DEV_7101&SUBSYS_71011849&REV_00\3&267A616A&0&39: ALi 7101 Power Management Controller
PCI\VEN_10DE&DEV_0391&SUBSYS_22201682&REV_A1\4&70BCEE6&0&0008: NVIDIA GeForce 7600 GT
PCI\VEN_1102&DEV_0004&SUBSYS_00531102&REV_03\4&3B8BE48B&0&3830: Creative SB Audigy
PCI\VEN_1102&DEV_4001&SUBSYS_00101102&REV_00\4&3B8BE48B&0&3A30: OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_1102&DEV_7003&SUBSYS_00401102&REV_03\4&3B8BE48B&0&3930: Creative Game Port
PCI\VEN_197B&DEV_2360&SUBSYS_03601849&REV_00\4&2FF59A88&0&0018: JMicron JMB36X Controller
24 matching device(s) found.
 
=========== 
USB devices 
=========== 
 
USB\ROOT_HUB\4&20A7D318&0                                   : USB Root Hub
USB\ROOT_HUB\4&336183BD&0                                   : USB Root Hub
USB\ROOT_HUB\4&4C9D2EC&0                                    : USB Root Hub
USB\ROOT_HUB20\4&1CE44A4&0                                  : USB Root Hub
USB\VID_03F0&PID_0305\CN0AT1I0R1DT                          : Hewlett-Packard ScanJet 4300C
USB\VID_03F0&PID_1204\HU0CF1G0V0JJ                          : USB Printing Support
USB\VID_045E&PID_00DB\5&1F10D2F&0&1                         : USB Composite Device
USB\VID_045E&PID_00DB&MI_00\6&1C848EDE&0&0000               : USB Human Interface Device
USB\VID_045E&PID_00DB&MI_01\6&1C848EDE&0&0001               : USB Human Interface Device
USB\VID_046D&PID_C50E\5&5AE8FC&0&1                          : Cordless USB Mouse
USB\VID_0E8F&PID_0003\5&1B59006F&0&2                        : XFX Game Controller
USBPRINT\HEWLETT-PACKARDDESKJET_930C\6&77EAA1F&0&USB001     : hp deskjet 930c series
12 matching device(s) found.

what is the defcon.exe for?

Last edited by ninouchka (2006-10-03 19:22:59)

Re: [NEEDS REPLY] 0x7B BSOD w/ JMicron JMB363 SATA RAID

hi

devcon.exe is Microsoft's windows setup API
(application programming interface)
http://en.wikipedia.org/wiki/Applicatio … _interface

I assume you used Meulc's dutch packs and Dutch addons in RVM.

the following is but a suggestion, so as to try figure out what caused the BSOD.
you definately need mass storage, but in your situation I would try it without the chipset pack.
I have had the issue with a flawed beta once (There're different chips in my rig, but I got an 0x00007B... the message TXT is quite general.)

Maybe you get past the BSOD if you don't use chipsets.
I dunno. Worth a shot?

The answer was 42?
Kind regards, Jaak.

Re: [NEEDS REPLY] 0x7B BSOD w/ JMicron JMB363 SATA RAID

another observance

it is not a good idea to run setup with live USB devices connected to the machine.

The answer was 42?
Kind regards, Jaak.

Re: [NEEDS REPLY] 0x7B BSOD w/ JMicron JMB363 SATA RAID

jtdoom wrote:

another observance

it is not a good idea to run setup with live USB devices connected to the machine.

You mean USB sticks or drives.
Mouse and keyboard, cams etc. , no problem.

Last edited by muiz3 (2006-10-04 02:02:38)

Re: [NEEDS REPLY] 0x7B BSOD w/ JMicron JMB363 SATA RAID

I removed my printer, scanner, and gamepad and gonna make it again.
And without the chipset pack.

Will post how it goes.

Re: [NEEDS REPLY] 0x7B BSOD w/ JMicron JMB363 SATA RAID

I made two bootable cds, one with only the rmv september update
and a second one with september update and the LAN and mass storage driver pack.

The first one installed fine when I setted my bios sata2 settings to emulate IDE (needed to, as there
are no sata2 drivers on the xp pro cd).
The second one with the driver pack and bios sata2 setting to SATA... nada.. again the BSOD screen.

Is it possible that the driver packs don't work on a dutch version of XP PRO?

Last edited by ninouchka (2006-10-04 10:04:53)

Re: [NEEDS REPLY] 0x7B BSOD w/ JMicron JMB363 SATA RAID

To which mass storage controller is the SATA HDD connected?

Founder of DriverPacks.net — wimleers.com

Re: [NEEDS REPLY] 0x7B BSOD w/ JMicron JMB363 SATA RAID

sata2 Seagate HD connected on sata2 controller JMicron JMB36X of an Asrock Dual939-sata2 mobo.
Sata2 setting is set in bios to sata.

Re: [NEEDS REPLY] 0x7B BSOD w/ JMicron JMB363 SATA RAID

Hi
just googled on the mobo, and the net returned a great many hits about people with boot problems.

here is a link to this model
http://www.asrock.com/product/939Dual-SATA2.htm
Wim may want to look at the supplied drivers...

as a temporary solution, I could suggest Nlite and winimage
winimage to extract the floppy image to a folder (for that F6 floppy)
nlite to integrate only the content that extracted floppy (like I once did for my mobo)

if you want to, driverpacks without mass storage/txtmode
test setup
post results

if it works that way, Bâshrat the Sneaky may want to look at the content of the F6 floppy and redo some filtering

Last edited by jtdoom (2006-10-15 09:31:56)

The answer was 42?
Kind regards, Jaak.

Re: [NEEDS REPLY] 0x7B BSOD w/ JMicron JMB363 SATA RAID

jtdoom,

the zip file for the JMicron_XP_2k(v207) doesnt contain a floppy image,
but a folder with the needed files.
In the readme.txt, this is mentioned,
If you want to build pre-install disk for windows,
copy directory "X32" and "X64" and file "JMicron", "txtsetup.oem" to floppy disk

So you mean that the problem is only related to the jmicron driver integrated in the mass storage
driver pack?
I will try to integrate the jmicron driver from asrock with nlite.
And after that integrate the driverpacks with dpbase but unchecking the txtmode for mass storage.
Is it that what you mean. Or not integrating the mass storage, only the others?
I want to use this install cd also for my other computers, so the mass storage driver pack would be very handy.

Will try nlite, this afternoon.

thanks for all the support!

Re: [NEEDS REPLY] 0x7B BSOD w/ JMicron JMB363 SATA RAID

Yesterday I had to install a pc with an ICH8R and a JMicron 363. It took me hours. It was the JMicron controller's driver: it was somehow resulting on BSODs. As soon as I removed the driver, and ONLY used the Intel driver (2 SATA drives were connected to the ICH8R in RAID0), it worked fine.

If you have the choice, DO NOT USE THE JMICRON CONTROLLER. But you do not have the choice... Good luck!

Founder of DriverPacks.net — wimleers.com

Re: [NEEDS REPLY] 0x7B BSOD w/ JMicron JMB363 SATA RAID

hi
it sure looks like the drivers are in the pack
and your device ID matches references I see in
d\m\j\2

you could compare driver version with what you find in that folder...
jraid.inf
;Copyright 2005, JMicron Technology Corp.

[Version]
Signature="$Windows NT$"
Provider=%JMICRON%
ClassGUID={4D36E97B-E325-11CE-BFC1-08002BE10318}
Class=SCSIAdapter
DriverVer=06/26/2006, 1.12.04.00   
CatalogFile=jraid.cat

the section on asrock

%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2360&SUBSYS_03601849  ; ASROCK
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2361&SUBSYS_03611849
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2363&SUBSYS_03631849
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_03651849
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2366&SUBSYS_03661849

%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2360&SUBSYS_23601849  ; ASROCK
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2361&SUBSYS_23611849
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2363&SUBSYS_23631849
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_23651849
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2366&SUBSYS_23661849

The answer was 42?
Kind regards, Jaak.

Re: [NEEDS REPLY] 0x7B BSOD w/ JMicron JMB363 SATA RAID

if the version does not match, then you could slipstream them using Nlite
I hope the mass storage pack will not clash with those

you could post the version you extracted.

The answer was 42?
Kind regards, Jaak.

Re: [NEEDS REPLY] 0x7B BSOD w/ JMicron JMB363 SATA RAID

in this mobo that mention, I had trouble to install O.S in SATA2 disc with JMicron connector, simply Disc doesn't boot, with or without drivers, Black Screen before Blue Screen Loads.... a real trouble, I was thinking in change discs, my SATA for boot and my SATA2 for info (my SATA in the ALI controller was recognized right, without any driver in IDE mode), thinking that my SATA2 disc was not able to boot, but a few days later, I changed my PC for an AM2 based A64, with nforce 410/Geforce 6100 based Chipset, and all is right, my S.O. is in SATA2 disc and all is right....

Experience: Jmicron is too bad...

Re: [NEEDS REPLY] 0x7B BSOD w/ JMicron JMB363 SATA RAID

Bionicmaster wrote:

in this mobo that mention, I had trouble to install O.S in SATA2 disc with JMicron connector, simply Disc doesn't boot, with or without drivers, Black Screen before Blue Screen Loads.... a real trouble, I was thinking in change discs, my SATA for boot and my SATA2 for info (my SATA in the ALI controller was recognized right, without any driver in IDE mode), thinking that my SATA2 disc was not able to boot, but a few days later, I changed my PC for an AM2 based A64, with nforce 410/Geforce 6100 based Chipset, and all is right, my S.O. is in SATA2 disc and all is right....

Experience: Jmicron is too bad...

Couldn't agree more smile

I will make the appropriate changes in DriverPack MassStorage, to reflect that JMicron is absolute crap: its drivers will NOT be loaded by default, brave souls will be able to renable them manually.

Founder of DriverPacks.net — wimleers.com

Re: [NEEDS REPLY] 0x7B BSOD w/ JMicron JMB363 SATA RAID

I have told before, the Jmicron controller has a bug in driverpacks that isn't correct yet. the txtsetup.sif is the cause of the Bsod!!

PCI\VEN_197B&DEV_2360="jraid"
PCI\VEN_197B&DEV_2361="jraid"
PCI\VEN_197B&DEV_2363="jraid"
PCI\VEN_197B&DEV_2365="jraid"
PCI\VEN_197B&DEV_2366="jraid"

This is the piece of txtsetup.sif, as you can see it load always RAID driver!!

change the "jraid" option with "jahci" option for your controller hwid.

I have Asrock 939Dual-Sata2 too and I have solved this by changing the first line

PCI\VEN_197B&DEV_2360="jraid"

to

PCI\VEN_197B&DEV_2360="jahci"

Bye.

Last edited by S3pHiroTh (2006-10-16 00:24:09)

Re: [NEEDS REPLY] 0x7B BSOD w/ JMicron JMB363 SATA RAID

hi
I had to leave for work, but just before I did, I looked at the drivers at the asrock site

i put the string posted in the hwid above into search
and this is indeed found in jahci.inf
VEN_197B&DEV_2360
the other F6 driver floppy has ALI

in driverpacks mass storage, this string is found in raid and jahci infs (and nowhere else)

thus, what S3pHiroTh posts makes sense to me.

The answer was 42?
Kind regards, Jaak.

Re: [NEEDS REPLY] 0x7B BSOD w/ JMicron JMB363 SATA RAID

jtdoom wrote:

hi
I had to leave for work, but just before I did, I looked at the drivers at the asrock site

i put the string posted in the hwid above into search
and this is indeed found in jahci.inf
VEN_197B&DEV_2360
the other F6 driver floppy has ALI

in driverpacks mass storage, this string is found in raid and jahci infs (and nowhere else)

thus, what S3pHiroTh posts makes sense to me.

I have done that me too... I have downloaded the driver from Asrock website (for found where is the problem in driverpacks for bsod) and the only difference between driverpacks and driver downloaded from asrock website, is what I have said before

Re: [NEEDS REPLY] 0x7B BSOD w/ JMicron JMB363 SATA RAID

Bâshrat the Sneaky wrote:
Bionicmaster wrote:

in this mobo that mention, I had trouble to install O.S in SATA2 disc with JMicron connector, simply Disc doesn't boot, with or without drivers, Black Screen before Blue Screen Loads.... a real trouble, I was thinking in change discs, my SATA for boot and my SATA2 for info (my SATA in the ALI controller was recognized right, without any driver in IDE mode), thinking that my SATA2 disc was not able to boot, but a few days later, I changed my PC for an AM2 based A64, with nforce 410/Geforce 6100 based Chipset, and all is right, my S.O. is in SATA2 disc and all is right....

Experience: Jmicron is too bad...

Couldn't agree more smile

I will make the appropriate changes in DriverPack MassStorage, to reflect that JMicron is absolute crap: its drivers will NOT be loaded by default, brave souls will be able to renable them manually.

I don't think it is fair to call jmicron crap just because the txtsetup.sif file is not created correctly when using driverpacks.

Re: [NEEDS REPLY] 0x7B BSOD w/ JMicron JMB363 SATA RAID

rayw69 wrote:
Bâshrat the Sneaky wrote:
Bionicmaster wrote:

in this mobo that mention, I had trouble to install O.S in SATA2 disc with JMicron connector, simply Disc doesn't boot, with or without drivers, Black Screen before Blue Screen Loads.... a real trouble, I was thinking in change discs, my SATA for boot and my SATA2 for info (my SATA in the ALI controller was recognized right, without any driver in IDE mode), thinking that my SATA2 disc was not able to boot, but a few days later, I changed my PC for an AM2 based A64, with nforce 410/Geforce 6100 based Chipset, and all is right, my S.O. is in SATA2 disc and all is right....

Experience: Jmicron is too bad...

Couldn't agree more smile

I will make the appropriate changes in DriverPack MassStorage, to reflect that JMicron is absolute crap: its drivers will NOT be loaded by default, brave souls will be able to renable them manually.

I don't think it is fair to call jmicron crap just because the txtsetup.sif file is not created correctly when using driverpacks.

I would agree with you, if this were the first time we had a bad JMicron experience. But I will look into that supposed txtsetup.sif error. I'd be very glad if that would solve everything, and then I would draw my words back as well. But I'm afraid we're not the only ones having this issue... Just google for JMicron BSOD and you'll find plenty of hits.

Founder of DriverPacks.net — wimleers.com

Re: [NEEDS REPLY] 0x7B BSOD w/ JMicron JMB363 SATA RAID

Bâshrat the Sneaky wrote:
rayw69 wrote:
Bâshrat the Sneaky wrote:

Couldn't agree more smile

I will make the appropriate changes in DriverPack MassStorage, to reflect that JMicron is absolute crap: its drivers will NOT be loaded by default, brave souls will be able to renable them manually.

I don't think it is fair to call jmicron crap just because the txtsetup.sif file is not created correctly when using driverpacks.

I would agree with you, if this were the first time we had a bad JMicron experience. But I will look into that supposed txtsetup.sif error. I'd be very glad if that would solve everything, and then I would draw my words back as well. But I'm afraid we're not the only ones having this issue... Just google for JMicron BSOD and you'll find plenty of hits.

Well, if that is the litmus test for whether or not something is crap or not, then every single brand is crap. I can type in the words "Nvidia" or "Intel" or "ATI" or "Promise" or anything else with "BSOD" into google and get a million results.

I posted this in another thread:

"By default, the driver pack does not have the JMicron controllers set up correctly. You need to edit the txtsetup.sif with the CC_0104 and CC_0106 suffixes, and also add CC_0101 to the exclusion list of both the jraid and jahci INF files."

It took me the better part of a day to figure out the above. Lots and lots of manual editing of the txtsetup.sif file and the various other SIF and .inf files. And multiple installations of Windows XP. When I discovered driverpacks and how to pre-load drivers, I literally had zero experience with txtsetup.oem files, and how to properly edit .inf files. This whole jmicron thing is really a simple problem, for a person with previous experience editing .inf files, and knows what the various suffixes for device IDs refer to.

I'd be willing to bet that there are other drivers in the mass storage driverpack which need the EXACT same kind of editing to work properly. Suppose there was a problem with the Highpoint driver in driverpacks. How would you ever find out? Not like any motherboard manufacturers are using Highpoint controllers.

It is just that the Jmicron controllers have become real popular lately with the new Intel southbridges that completely eliminate IDE support. Just about every damn Intel board using ICH8/ICH8R is going to have a Jmicron controller integrated for IDE support. The large number of people having problems with Jmicron is simply a reflection of the large number of motherboard manufacturers who are now using Jmicron. If by chance, my motherboard didn't include the Jmicron controller, or I had simply no chosen to use it, then I'd never think there was a problem with the driverpacks.

Anyways, I hope you'll be able to implement the above fixes into the next version of the mass storage driver pack. I think the fact that Jmicron is becoming more and more popular by the day is not a reason to make Jmicron drivers not load by default. If anything, it should be a reason to work harder to find a solution.

Re: [NEEDS REPLY] 0x7B BSOD w/ JMicron JMB363 SATA RAID

rayw69 wrote:

I posted this in another thread:

"By default, the driver pack does not have the JMicron controllers set up correctly. You need to edit the txtsetup.sif with the CC_0104 and CC_0106 suffixes, and also add CC_0101 to the exclusion list of both the jraid and jahci INF files."

Could you post a global topic to explain in details what exactly you modify in txtsetup.sif to use JMicron controler ? Thanks for all
Best regards from France...

http://img136.imageshack.us/img136/9877/cocciwayoflifero0.jpg