Jump to content











Photo
- - - - -

Is there a tutorial on WinXP-bootable ExpressCard SSD out there?


  • Please log in to reply
108 replies to this topic

#26 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14950 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 25 February 2010 - 07:15 PM

NOVAES,
I am not getting it.
If you want to install Windows XP on that card, you need to integrate the needed drivers, what do you mean by:

All my attempts to install XP Pro on the SSD not worked, cause XP Installer not find the card (nlighting xp-sony-driver + hitachi microdrive filter driver *inside xp the card becomes with the second "fixed" *).


:lol:

Of course HP USB Format tool won't work, but it is also now deprecated as new and "better" apps are available.

Asterisk never came back to report success. :rolleyes:

We need some more details on the actual card and on it's driver, like WHERE is it available in order to hopefully try and help you.

:rolleyes:

Wonko

#27 guustf

guustf

    Newbie

  • Members
  • 14 posts
  •  
    Belgium

Posted 25 February 2010 - 07:26 PM

Hi !

Driver for the SxS Pro is there: http://www.sony.ca/p...dia/drivers.htm

http://www.thinkwiki...lash_boot_drive

After the install is finished you will need to install the Hitachi microdrive disk drivers (google for XPfildrvr1224.zip), which will mask the removable bits and should allow suspend and other operations that fail on a removable drive to work.


=> so I could made pagefile on it cause xp thinks it is a fixed drive

#28 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14950 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 25 February 2010 - 07:44 PM

Ok, let's separate the issues.

Forget for the moment about the Filter Driver.

What is the problem with integrating the Sony driver in the Source?

Maybe this:
http://www.sony.ca/p...dia/drivers.htm

Before beginning the following procedure, ensure that the SxS PRO is disconnected from the computer. During the installation of this update, be sure that you are logged in as the administrator or as a user with administrative rights. To ensure that no other program interferes with the installation, save all work and close all other programs. The taskbar should be clear of applications before proceeding.

creates problems? :lol:

How (meaning "how", i.e. which source, CD, USB stick, what install method, like "boot media", WINNT.EXE form DOS, WINNT32.EXE form PE, etc.) did you try?

Are you using the thinkpad or a "normal" desktop to prepare/format/whatever the card?

Have you seen/attempted the approach of using firadisk+F6 floppy drive mapped with grub4dos to have the drivers available?

:rolleyes:

Wonko

#29 guustf

guustf

    Newbie

  • Members
  • 14 posts
  •  
    Belgium

Posted 25 February 2010 - 08:00 PM

Forget for the moment about the Filter Driver.


Ok.

How (meaning "how", i.e. which source, CD, USB stick, what install method, like "boot media", WINNT.EXE form DOS, WINNT32.EXE form PE, etc.) did you try?


Using modified nLight ISO => I've integrated the driver...but maybe no success cause missing txtsetup.oem in the package:

SxSmemcd.cat; SxSmemcd.ico (looks good ;-); SxSmemcd.inf; SxSmemcd.sys

Are you using the thinkpad or a "normal" desktop to prepare/format/whatever the card?


the thinkpad with normal xp desktop; linux not recognizing the card

Have you seen/attempted the approach of using firadisk+F6 floppy drive mapped with grub4dos to have the drivers available?


No, I've never heard before. the driver cannot work in dos...can grub load xp driver? Also the PCIe-Bus-Driver from intel-chipset must be loaded to...

:lol:

novaes

#30 guustf

guustf

    Newbie

  • Members
  • 14 posts
  •  
    Belgium

Posted 25 February 2010 - 08:03 PM

;
; SxSmemcd.inf : SxS Memory Card Driver
;
; Copyright 2007 Sony Corporation
;

[Version]
Signature = "$Windows NT$"
Class = MTD
ClassGuid = {4D36E970-E325-11CE-BFC1-08002BE10318}
Provider = %SONY%
DriverVer = 07/25/2007,1.00.01.0
CatalogFile = SxSmemcd.cat

[Manufacturer]
%SONY% = SxS_SONY, NTx86
%SANDISK% = SxS_SANDISK, NTx86

[SxS_SONY.NTx86]
%PRODUCT_DESC% = SxSmemcd.Install, PCI\VEN_104D&DEV_81CE&SUBSYS_81CE104D

[SxS_SANDISK.NTx86]
%PRODUCT_DESC% = SxSmemcd.Install, PCI\VEN_104D&DEV_81CE&SUBSYS_100115B7

[SxSmemcd.Install]
CopyFiles = SxSmemcd.sys.CopyFiles
CopyFiles = SxSmemcd.ico.CopyFiles

[SxSmemcd.Install.Services]
AddService = SxSmemcd, 0x00000002, SxSmemcd.Service

[SxSmemcd.Install.HW]
AddReg = SxSmemcd.Install.AddReg

[SxSmemcd.sys.CopyFiles]
SxSmemcd.sys,,,

[SxSmemcd.ico.CopyFiles]
SxSmemcd.ico,,,

[SxSmemcd.Service]
DisplayName = %PRODUCT_DISP_NAME%
ServiceType = %SERVICE_KERNEL_DRIVER%
StartType = %SERVICE_DEMAND_START%
ErrorControl = %SERVICE_ERROR_NORMAL%
ServiceBinary = %12%\SxSmemcd.sys
AddReg = SxSmemcd.Service.AddReg

[SxSmemcd.Install.AddReg]
HKR, , "RemovalPolicy", %FLG_ADDREG_TYPE_DWORD%, %POLICY_ExpectSurpriseRemoval%

HKLM, %REGKEY_PER_HW_ID%, %REGVAL_NO_SE%, %FLG_ADDREG_TYPE_DWORD%, %VALUE_SxS_NO_SE%
HKLM, %REGKEY_PER_HW_ID%, %REGVAL_ICONS%, %FLG_ADDREG_TYPE_MULTI_SZ%, %VALUE_SxS_ICONS%
HKLM, %REGKEY_PER_HW_ID%, %REGVAL_LABEL%, %FLG_ADDREG_TYPE_SZ%, %VALUE_SxS_LABEL%

[SxSmemcd.Service.AddReg]

[SourceDisksNames]
1 = %PRODUCT_DESC% %SOURCE_DISK_DESC%,,,

[SourceDisksFiles]
SxSmemcd.sys = 1,,,,,
SxSmemcd.ico = 1,,,,,

[DestinationDirs]
SxSmemcd.sys.CopyFiles = 12 ; %windir%/System32/Drivers
SxSmemcd.ico.CopyFiles = 10 ; %windir%

[Strings]
SONY = "Sony Corporation"
SANDISK = "SanDisk Corporation"
PRODUCT_DESC = "SxS Memory Card"
PRODUCT_DISP_NAME = "SxS Memory Card"
SOURCE_DISK_DESC = "Source Disk #1"

REGKEY_PER_HW_ID = "SOFTWARE\Microsoft\Windows NT\CurrentVersion\PerHwIdStorage\PCI#VEN_104D&DEV_81CE"

REGVAL_NO_SE = "NoSoftEject"
REGVAL_ICONS = "Icons"
REGVAL_LABEL = "Label"

VALUE_SxS_NO_SE = 1
VALUE_SxS_ICONS = "%SystemRoot%\SxSmemcd.ico"
VALUE_SxS_LABEL = "SxS Memory Card"

SERVICE_KERNEL_DRIVER = 1
SERVICE_FILE_SYSTEM_DRIVER = 2
SERVICE_ADAPTER = 4
SERVICE_WIN32_OWN_PROCESS = 10
SERVICE_WIN32_SHARE_PROCESS = 20

SERVICE_BOOT_START = 0
SERVICE_SYSTEM_START = 1
SERVICE_AUTO_START = 2
SERVICE_DEMAND_START = 3
SERVICE_DISABLE = 4

SERVICE_ERROR_IGNORE = 0
SERVICE_ERROR_NORMAL = 1
SERVICE_ERROR_SEVERE = 2
SERVICE_ERROR_CRITICAL = 3

FLG_ADDREG_BINVALUETYPE = 0x00000001
FLG_ADDREG_NOCLOBBER = 0x00000002
FLG_ADDREG_DELVAL = 0x00000004
FLG_ADDREG_APPEND = 0x00000008
FLG_ADDREG_KEYONLY = 0x00000010
FLG_ADDREG_OVERWRITEONLY = 0x00000020
FLG_ADDREG_64BITKEY = 0x00001000
FLG_ADDREG_KEYONLY_COMMON = 0x00002000
FLG_ADDREG_32BITKEY = 0x00004000

FLG_ADDREG_TYPE_SZ = 0x00000000
FLG_ADDREG_TYPE_MULTI_SZ = 0x00010000
FLG_ADDREG_TYPE_EXPAND_SZ = 0x00020000
FLG_ADDREG_TYPE_DWORD = 0x00010001
FLG_ADDREG_TYPE_NONE = 0x00020001

POLICY_ExpectOrderlyRemoval = 2
POLICY_ExpectSurpriseRemoval = 3



#31 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14950 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 25 February 2010 - 08:08 PM

Time to start reading:
http://www.osronline...tsetup_1wmq.htm
http://support.micro...kb/318812/en-us
http://support.micro...kb/288344/en-us

You need a txtsetup.oem, if the package misses it, you can create one.

Wonko

#32 guustf

guustf

    Newbie

  • Members
  • 14 posts
  •  
    Belgium

Posted 25 February 2010 - 08:37 PM

Aahh, I understand. The FiraDisk solution is working with kickstarter-image...right?

thank you so far :rolleyes:

good, I loaded the SCSICFGSET

in $OEM$\TEXTMODE I put in the driver-files

what I should do in $OEM$\$1 ? the same ?


Ok, here my own txtsetup.oem:

# This file contains the minimum required entries for TXTSETUP.OEM.
# This is only an example..you should use the TXTSETUP.OEM supplied by the
# vendor. However, it will be necessary to change the entry(ies) in the
# [Disks] section of the vendor's TXTSETUP.OEM to the following format as
# you see below:
#
# [Disks]
# d1="<diskette description>",\<tagfile>, \
# ...
# dn="<diskette description>",\<tagfile>, \
#
#
# For FAT32 preinstallations, the entries should look like:
#
# d1="<diskette description>",<tagfile>, .
# ...
# dn="<diskette description>",<tagfile>, .

[Disks]
d1 = "Windows 2000 Driver Set v1.00", w2kdsk1, \

[Defaults]
scsi = SCSI_xp

[scsi]
SCSI_xp = "Sony SxS Pro 16 GB"

[Files.scsi.SCSI_xp]
driver = d1, SxSmemcd.sys, SCSIDRV
inf = d1, SxSmemcd.inf
catalog = d1, SxSmemcd.cat

# In the [HardwareIds...] section
# xxxx refers to the vendorID Number
# yyyy refers to the device ID Number
# as in: PCI\VEN_1234&DEV_4567
# Note: This section should already be configured for you by the vendor.

[HardwareIds.scsi.SCSIDRV_xp]
id="SxSmemcd\Disk&Ven_Sony&Prod_SxS", "SCSIDRV"

[Config.SCSIDRV]
value = "", Tag, REG_DWORD, 1



What I should enter in the config-section, I not really understand... :lol:


[Config.DriverKey]
value = subkey_name,value_name,value_type,value
...

subkey_name
Specifies the name of a key under the Services\DriverKey tree where Setup places the specified value. Setup creates the key if it does not exist.

If subkey_name is the empty string (""), the value is placed under the Services\DriverKey.

The subkey_name can specify more than one level of subkey, such as "subkey1\subkey2\subkey3".
value_name
Specifies the name of the value to be set.
value_type
Specifes the type of the registry entry. The value_type can be one of the following:

REG_DWORD
One value is allowed; it must be a string containing up to eight hexadecimal digits.

For example:

value = parameters,NumberOfButtons,REG_DWORD,2


REG_SZ or REG_EXPAND_SZ
One value is allowed; it is interpreted as the zero-terminated string to be stored.

For example:

value = parameters,Description,REG_SZ,"This is a text string"


REG_BINARY
One value is allowed; it is a string of hex digits, each pair of which is interpreted as a byte value.

For example (stores the byte stream 00,34,ec,4d,04,5a):

value = parameters,Data,REG_BINARY,0034eC4D045a


REG_MULTI_SZ
Multiple value arguments are allowed; each is interpreted as a component of the MULTI_SZ string.

For example:

value = parameters,Strings,REG_MULTI_SZ,String1,"String 2",string3


value
Specifies the value; its format depends on value_type.

The following example shows a Config.DriverKey section:

; ...
[Config.OEMSCSI]
value = parameters\PnpInterface,5,REG_DWORD,1
; ...



#33 guustf

guustf

    Newbie

  • Members
  • 14 posts
  •  
    Belgium

Posted 25 February 2010 - 08:44 PM

Sorry for my bad knowledge about this things...hope you will not do this now :lol:
Posted Image

#34 guustf

guustf

    Newbie

  • Members
  • 14 posts
  •  
    Belgium

Posted 25 February 2010 - 09:09 PM

Sorry, it just should be a joke. If you want to go to sleep now...maybe you could help me tomorrow. Good night!

#35 guustf

guustf

    Newbie

  • Members
  • 14 posts
  •  
    Belgium

Posted 25 February 2010 - 11:50 PM

ok, little success: xp installer shows my integrated driver loading after the F6 key prompt and before F8 license agreement (xp pro installation)

but the disc (sony sxs) will not show :lol:

here my txtsetup.oem

[Disks]
d1 = "Sony SSD Driver Disk", \SxSmemcd, .

[Defaults]
scsi = SCSI_xp

[scsi]
SCSI_xp = "Sony SxS Pro 16 GB"

[Files.scsi.SCSI_xp]
driver = d1, SxSmemcd.sys, SxSmemcd
inf = d1, SxSmemcd.inf
catalog = d1, SxSmemcd.cat

[HardwareIds.scsi.SxSmemcd_xp]
id="PCI#VEN_104D&DEV_81CE", "SxSmemcd"

[Config.SxSmemcd_xp]
value = "", Tag, REG_DWORD, 1


maybe reason
a ) wrong hardware-id. where I can find the correct one, I'm not totally sure? registry...
b ) something wrong with the txtsetup.oem
c ) ssd is not correct bootable formated, which modern tool I can use?
d ) PCIe driver must be integrated to (nlite.iso)

#36 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14950 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 26 February 2010 - 08:40 AM

Boy, are you a fast learner! :rolleyes:

Let's see:

maybe reason
a ) wrong hardware-id. where I can find the correct one, I'm not totally sure? registry...
b ) something wrong with the txtsetup.oem
c ) ssd is not correct bootable formated, which modern tool I can use?
d ) PCIe driver must be integrated to (nlite.iso)


a. possible, though the problem might be of a more complex kind (like the need of a "double" driver, one for the BUS and one for the stoopid Sony card), try using SIW or SIV to determine the ID and to which BUS it is connected:
http://www.gtopala.com/
http://rh-software.com/
b. possible, though you should have an error.
c. no, that should not be relevant, the partitioning/formatting should be possible also within setup, or at the worst, the drive should be shown in the list of available drives and later fail when you select it :rolleyes:
d. yep, that -see also point a. above - could be the problem.

Once you now have a txtsetup.oem, you can try integrating BOTH the SXS and the Pci-e driver with nlite.

More generally, you will need some patience AFAIK this is highly experimental, and probably the first time we have to deal with that strange hardware, a number of other members are more expert/qualified than me when it comes to driver integration, they will probably notice this thread and take part to the game in a few days time.

As I see it there are several layers of *unfamiliar* things like:
  • PCIe bus
  • SXS
  • possibly some quirk in the Lenovo BIOS

About partitioning/formatting if I were you I would use an indirect method, by creating an image and partitioning/formatting it, check here:
http://www.boot-land...?showtopic=5000
http://www.boot-land...?showtopic=3191
http://www.boot-land...?...c=5000&st=1
and "translate" the info from USB to SXS.

But I don't think that this is the problem right now.

:rolleyes:

Wonko

#37 guustf

guustf

    Newbie

  • Members
  • 14 posts
  •  
    Belgium

Posted 26 February 2010 - 07:39 PM

Boy, are you a fast learner! :rolleyes:

:rolleyes: :rolleyes: :lol:

THANX for your introduction, wonko. ;)

-----------------------------------------------------------------------
For those who're interested in the topic: I made this 2 txtsetupoems and nlited them into iso, but it didn't work. The sxs as textmode and the intel pcie as PnP. For the intel driver I only have a *.cat and a *.inf-file, but theres no *.sys for. Maybe a reason?

txtsetup.oem for the SxS Disk

[Disks]
d1 = "Sony SSD Driver Disk", \SxSmemcd, .

[Defaults]
scsi = SCSI_xp

[scsi]
SCSI_xp = "Sony SxS Pro 16 GB"

[Files.scsi.SCSI_xp]
driver = d1, SxSmemcd.sys, SxSmemcd
inf = d1, SxSmemcd.inf
catalog = d1, SxSmemcd.cat

[HardwareIds.scsi.SxSmemcd_xp]
id="PCI\VEN_104D&DEV_81CE", "SxSmemcd"

[Config.SxSmemcd_xp]
value = "", Tag, REG_DWORD, 1


txtsetup.oem for the Intel PCIe Driver

[Disks]
d1 = "Intel PCI Express for SSD", \ich7core, .

[Defaults]
scsi = SCSI_xp2

[scsi]
SCSI_xp2 = "Intel PCI Express for SSD"

[Files.scsi.SCSI_xp2]
inf = d1, ich7core.inf
catalog = d1, ich7core.cat

[HardwareIds.scsi.ich7core_xp]
id="PCI\VEN_8086&DEV_27D4", "ich7core"

[Config.ich7core_xp]
value = "", Tag, REG_DWORD, 1



a. possible, though the problem might be of a more complex kind (like the need of a "double" driver, one for the BUS and one for the stoopid Sony card), try using SIW or SIV to determine the ID and to which BUS it is connected:

the IDs are correct now

b. possible, though you should have an error.

anybody see an error above?

Once you now have a txtsetup.oem, you can try integrating BOTH the SXS and the Pci-e driver with nlite.

I tried seperatly, maybe together?

More generally, you will need some patience AFAIK this is highly experimental, and probably the first time we have to deal with that strange hardware, a number of other members are more expert/qualified than me when it comes to driver integration, they will probably notice this thread and take part to the game in a few days time.

  • PCIe bus
  • SXS
  • possibly some quirk in the Lenovo BIOS

there's the possibility to modify lenovo bios?

#38 guustf

guustf

    Newbie

  • Members
  • 14 posts
  •  
    Belgium

Posted 03 March 2010 - 07:46 PM

*PUSH*

anybody out there with an idea? :exclamation:

#39 shiggidy_

shiggidy_

    Member

  • Members
  • 55 posts
  •  
    Solomon Islands

Posted 08 March 2010 - 09:12 AM

With this txtsetup.oem it is working!

; Copyright © 2003-08 Intel Corporation
;#############################################################################
;#
;# Filename: TXTSETUP.OEM
;#
;#############################################################################
[Disks]
disk1 = "++++ Sony SxS Pro 16 GB", SxSmemcd.sys, \

[Defaults]
scsi = iaStor_8ME9ME5

;#############################################################################
[scsi]

; SxSmemcd.inf
iaStor_8ME9ME5 = "Sony SxS Pro 16 GB"

;#############################################################################

; SxSmemcd.inf
[Files.scsi.iaStor_8ME9ME5]
driver = disk1, SxSmemcd.sys, SxSmemcd
inf = disk1, SxSmemcd.inf
catalog = disk1, SxSmemcd.cat

;#############################################################################
[Config.SxSmemcd]
value = "", tag, REG_DWORD, 1b
value = "", ErrorControl, REG_DWORD, 1
value = "", Group, REG_SZ, "SCSI Miniport"
value = "", Start, REG_DWORD, 0
value = "", Type, REG_DWORD, 1

;#############################################################################

; SxSmemcd.inf
[HardwareIds.scsi.iaStor_8ME9ME5]
id = "PCI\VEN_104D&DEV_81CE&SUBSYS_81CE104D","SxSmemcd"



But XP installer says something like "computer startup program cannot read hdd, partition or freespace".

Is the reason the missing mbr on the SXS drive or the missing bios support for PCIe? What can I do to solve?

#40 shiggidy_

shiggidy_

    Member

  • Members
  • 55 posts
  •  
    Solomon Islands

Posted 09 March 2010 - 04:53 PM

After googling it seems that the ssd (sxs) cannot controlled via 0x80 (so the XP installer complains).

I tried MBRBatch (jaclazz), it writes the vdk image to the sxs card but it doesn't work...any idea?

#41 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14950 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 09 March 2010 - 06:35 PM

On behalf of jaclaz ;)I can tell you that:
  • MBRBATCH does NOT create a "vdk" image
  • MBRBATCH does NOT write it to a \\physicaldrive, but only on a filesystem

So maybe you failed to describe what you did or you did something else. :ranting2:

I get that you managed to have a working txtsetup.oem, which is a GOOD thing :ranting2: , but from that to directy install to it an XP there is a loooong way.

Check the original Tutorials by Dietmar, where XP was installed on "conventional" media and then imaged to USB, that is the way that is most likely to work at this stage:
http://www.911cd.net...showtopic=14181

:ranting2:

Wonko

#42 shiggidy_

shiggidy_

    Member

  • Members
  • 55 posts
  •  
    Solomon Islands

Posted 10 March 2010 - 06:34 PM

Hi wonko!

So maybe you failed to describe what you did or you did something else. :ranting2:


I experimented with jaclaz MBRBatch Release, the link you posted to me on Feb 26 2010, 08:40 AM, see above...

I get that you managed to have a working txtsetup.oem, which is a GOOD thing :ranting2: , but from that to directy install to it an XP there is a loooong way.


I've an idea of it now. I checked Dietmars Tutorials, especially No.7 ... "Boot from USB/Firewire HD without BIOS support, Fake Signature Method" => It's the only way, right?

This entry of Dietmar seems to me the solution:

I chose a fresh install of XP and copied this XP direct after installation to the USB harddisk. It is sitting on the USB harddisk not USB boot friendly. I changed nothing on the USB XP, it is just the copied normal XP installation.

Only XP.IMG was made USB boot friendly: Import Hive SYSTEM from XP.IMG, sitting on the virtual 50 MB disk, call it otto, delete HKLM\otto\ControlSet001\Control\CriticalDeviceDatabase and use the attached otto.reg file.
In otto\ControlSet001\Services set all USB drivers Start=0 and Group System Reserved, thats all,
because, there are no USB *.inf files in XP.IMG.
Delete the key HKLM\otto\MountedDevices.
Unload the HIVE otto back to XP.IMG on virtual Harddisk, rename there otto to SYSTEM.


=> As I understand the mini-XP from kicker-image must 'think' the SSD (in this term Sony SxS) is a normal atapi hdd. Right? So in fact you must change registry of kicker-image. But I've really no idea how I can modify the "otto.reg" in Dietmars Post for booting from PCIe instead USB.

And, for understanding, I'm not sure about how kicker-image give the boot-job to the xp on ssd...

:ranting2:

#43 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14950 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 12 March 2010 - 06:22 PM

The general idea of the "fake signature method" or "XP Kansas City Shuffle" is the following:
  • you have some media, any media, that supports "HD like" format AND is normally accessible/bootable/can have XP installed to it.
  • you start booting it, then by a clever trick of the hand (which is faster than the eye, and definitely faster than stoopid XP) you exchange the media, or rather you make XP think it is booting form the original media from which you started booting, but you actually make it boot to another one

The next problem is finding the entries needed to make the XP install "PCIe/SSD friendly".

Basically it should mean having an install that actually "normally" supports the BUS/DEVICE and change the starting order of the related services, giving them a higher priority, typically "BootBusExtender" instead of the whatever they have normally.

Read the "XP Kansas City Shuffle" related threads to better get the idea, links can be found here:
http://www.911cd.net...showtopic=21891
http://www.911cd.net...showtopic=21939
http://www.boot-land...?...ic=5487&hl=


:ranting2:

Wonko

#44 shiggidy_

shiggidy_

    Member

  • Members
  • 55 posts
  •  
    Solomon Islands

Posted 14 March 2010 - 08:26 PM

Oh wonko, that's to much to me :cheers: I will give up... Only in theorie I understand everything and can also 'see' the solution...

I cloned my working xp (inside all needed drivers) to the PCIe SSD (SxS): But how to modify driver/registry in detail for functional booting?
I found a tutorial, but I cannot translate it to SxS Driver cause its very different... tutorial
Only Success: The SxS-Driver works perfectly in WIN-PE (read/write) tested with BartPE-CD.

=> Someone should write a tool (putting together all ideas of chainload, pe2usb etc.) so that the enduser only have to choose the source (a device with a working installed xp) and a target physical drive (all physically drives inside windows)...

The *dreaming* :lol: tool should do automaticly create virtual drive to copy in pe-bootfiles from source drive, making bootfriendly, creating kickerimage with grub, do fakesignature, AND install the image on working bootdevice (normally hdd) as a xp boot loader entry in one way! So you can boot from everything, except stones, animals, womens and those things ;-)

The only thing user has to do then is cloning working xp system partition to new physically drive (which has no bios boot support). For modify XP installation working on the new drive (driver, registry) a step by step tutorial would very helpfull... > acronis true imag with universal restore e.g. can clone a hdd image to a new pc by putting in new sotrage drivers...(I used to transfer system from ide to sata a long time ago)


=> Thats a lot of work but in the end it will become famous like bartpe himself maybe ;) ;) :cheers:

#45 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14950 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 14 March 2010 - 09:06 PM

Well, you have to try.

The tutorial you linked to is mish/mash of various other that have NOTHING to do with SD, that tutorial is simply about USB booting, as the eeepc, to which is referred has a a SD internal slot that is connected through (internal) USB.

Which are the services involved in SXS?

Which Priority do they have?

Try changing it on a working (NOT on SSD) XP to BootBusExtender.

If there are no problems, try replicating the same settings to the image you made on SSD.

Then, create a XP Kansas City Shuffle booting image.

Unfortunately all I can help you with is the latter item.

:lol:

Wonko

#46 cdob

cdob

    Gold Member

  • Expert
  • 1440 posts

Posted 14 March 2010 - 10:09 PM

I cloned my working xp (inside all needed drivers) to the PCIe SSD (SxS):

That's nice.

Can you verify registry:
Does exist HKLM\SYSTEM\CurrentControlSet\Services\SxSmemcd ?
Is HKLM\SYSTEM\CurrentControlSet\Services\SxSmemcd\Start set to 0 ?
Does exist HKLM\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_104D&DEV_81CE ?

Given all three conditions you may continue at ChainBootXP:
http://www.boot-land...?...ost&p=68173
The Script should create a kickerimage to your PCIe SSD.
It's up to you to install the image on working bootdevice.

#47 shiggidy_

shiggidy_

    Member

  • Members
  • 55 posts
  •  
    Solomon Islands

Posted 14 March 2010 - 10:41 PM

Given all three conditions you may continue at ChainBootXP:

All given :cheers:

The Script should create a kickerimage to your PCIe SSD.

Yippie!!!

Is there an help file? Sorry, I'm confused...What must be entered there?

Posted Image

THX :lol:

#48 shiggidy_

shiggidy_

    Member

  • Members
  • 55 posts
  •  
    Solomon Islands

Posted 14 March 2010 - 10:50 PM

Which are the services involved in SXS?


I found this in registry for sxs

Posted Image

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DIFx\DriverStore\SxSmemcd_10839D313B92C4F349EAFBF9CD57F596D7A87A1B]
"creation"=hex:78,d4,63,f6,f1,95,ca,01
"type"=dword:00000006
"INF"="SxSmemcd.inf"
"Services"=hex(7):53,00,78,00,53,00,6d,00,65,00,6d,00,63,00,64,00,00,00,00,00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\PerHwIdStorage\PCI#VEN_104D&DEV_81CE]
"NoSoftEject"=dword:00000001
"Icons"=hex(7):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,\
00,25,00,5c,00,53,00,78,00,53,00,6d,00,65,00,6d,00,63,00,64,00,2e,00,69,00,\
63,00,6f,00,00,00,00,00
"Label"="SxS Memory Card"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\sxsmemcd#disk&ven_sony&prod_sxs]
"ClassGUID"="{4D36E967-E325-11CE-BFC1-08002BE10318}"
"LowerFilters"=hex(7):63,00,66,00,61,00,64,00,69,00,73,00,6b,00,00,00,00,00
"Service"="disk"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\DeviceClasses\{53f56307-b6bf-11d0-94f2-00a0c91efb8b}\##?#SxSmemcd#Disk&Ven_Sony&Prod_SxS#5&efdfa4f&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}]
"DeviceInstance"="SxSmemcd\\Disk&Ven_Sony&Prod_SxS\\5&efdfa4f&0"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\DeviceClasses\{53f56307-b6bf-11d0-94f2-00a0c91efb8b}\##?#SxSmemcd#Disk&Ven_Sony&Prod_SxS#5&efdfa4f&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}\#]
"SymbolicLink"="\\\\?\\SxSmemcd#Disk&Ven_Sony&Prod_SxS#5&efdfa4f&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}"

and so on...

Which Priority do they have?

3

Try changing it on a working (NOT on SSD) XP to BootBusExtender.

How?

Unfortunately all I can help you with is the latter item.

THX a lot

#49 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14950 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 15 March 2010 - 10:00 AM

Some minor disambiguation.

Connect to your PC a USB stick or USB hard disk.

Go to "Device Manager".

Select to see devices by connection.

You'll probably have an entry like "ACPI multiprocessor PC".

Expand it.

Find your device.

The actual device will be found in a tree like (I have not an English system handy right now, terms might be slightly different):
ACPI multiprocessor PC->PCI bus->USB EHCI COntroller->Main USB hub->USB Mass Storage device->Your actual device->Disk

Now, click on each of the item of the trees and see which driver is used.
From the bottom up (bolded are the "relevant ones"):
  • Volsnap.sys
  • Disk.sys
  • Partmgr.sys
  • Usbstor.sys
  • Usbhub.sys
  • Usbd.sys
  • Usbehci.sys
  • Usbhub.sys
  • Usbport.sys
  • hccoin.dll
  • Usbui.dll
  • pci.sys

Now, these drivers can be found in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services which is normally a mirror of HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services (changes should be made to the mirrored set, i.e. ControlSet00x as defined in HKEY_LOCAL_MACHINE\SYSTEM\Select )

Some will have a "Group", to follow the example, usbhub has group "Base".
All will have a "Start", to follow the example, usbhub has Start=0x3.

Pci.sys has "Group" "Boot Bus Extender" and Start=0x0

If you re-read the linked to "USB oriented" tutorials you will see how the "main point" is that the "Group" of the main drivers involved has to be changed from "Base" to "Boot Bus Extender" (but "SCSI Miniport" may also work for SxSmemcd.sys) and "Start" has to be changed from "0x3" to "0x0" (which means start automatically).

This "Group" is what sometimes is referred to as "Load order group" or "Load Priority" or simply "priority".

You have to make sure that the involved needed drivers have such settings.

Read, understand, do experiments:
http://www.boot-land...amp;#entry68173

After cloning the drive:
run ChainBoot script
select source directory: your USB SSD windows %SystemRoot%
select add pcmcia boot driver
select "reset USB driver config (CriticalDeviceDatabase and Services)"
disable create ISO file
enable copy Image to
select your boot.ini drive, maybe c:
enable add entry to menu.lst
....



:cheers:

Wonko

#50 cdob

cdob

    Gold Member

  • Expert
  • 1440 posts

Posted 15 March 2010 - 08:25 PM

All given

I wonder: the pictures shows different conditions

Picture indicates:
Service sxsmemcd start is set to 3, that's not 0.
sxsmemcd is not mentioned at CriticalDeviceDatabase.

Apply this to running windows
REGEDIT4



&#91;HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_104D&DEV_81CE&#93;

&#34;ClassGUID&#34;=&#34;{4D36E970-E325-11CE-BFC1-08002BE10318}&#34;

&#34;Service&#34;=&#34;SxSmemcd&#34;



&#91;HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SxSmemcd&#93;

&#34;Type&#34;=dword&#58;00000001

&#34;Start&#34;=dword&#58;00000000

&#34;ErrorControl&#34;=dword&#58;00000001

&#34;DisplayName&#34;=&#34;SxS Memory Card&#34;

&#34;ImagePath&#34;=&#34;system32\\DRIVERS\\SxSmemcd.sys&#34;

&#34;Group&#34;=&#34;SCSI miniport&#34;

Cone again your working XP to the PCIe SSD (SxS).

A LowerFilters cfadisk is connected to sxsmemcd#disk&ven_sony&prod_sxs

Why did you add cfadisk?
Do you use several partitions at SSd card?
Which partitions does windows use?

Is there an help file? Sorry, I'm confused...What must be entered there?

Source directory: select %SystemRoot% directory at your PCIe SSD card.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users