108 replies to this topic

[shiggidy_]

@Wonko: I think for my term it's only sysmemcd.sys as service (driver used), cause in BartPE-Booting-Test the PCIe-Driver was integrated...
But the Post was good for understanding!

@cdob: I changed registry with posted reg-content > system normally booting w/o problem (ssd works) > cloned hdd again
In your previous post I read only if the string exist, not if its set to 0, so that was mean by 'all given', sorry

The 'LowerFilters cfadisk' (Hitachi Storage Driver) I used for making XP thinking its real harddrive, not a removeable ssd...
=> I uninstalled all, so definetly CriticalDeviceDatabase\PCI#VEN_104D&DEV_81CE

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

OK, I run script with this conditions:

Source: SSD-Drive-Letter:\Windows
copy chainboot image to C:\
add entry to menu.lst
add kernel and hal -KB309283

Script stops und abort at point: execute ImageCopyFilesXP.cmd > 'copy files failed'

> Is it a problem with path?

[Wonko the Sane]

Script stops und abort at point: execute ImageCopyFilesXP.cmd > 'copy files failed'

> Is it a problem with path?

It comes from this:

// copy textmode boot files to mounted image
ExtractFile,"%ScriptFile%","Folder","ImageCopyFilesXP.cmd","%ProjectTemp%"
Echo,"execute ImageCopyFilesXP.cmd - read %ProjectTemp%\ImageCopyFilesXP.log"
System,CURSOR,WAIT
ShellExecute,hide,"%ProjectTemp%\ImageCopyFilesXP.cmd","#$q%SourceDir%#$q %FreeDrive% > #$q%ProjectTemp%\ImageCopyFilesXP.log#$q"
System,CURSOR,Normal
If,NotExistFile,"%FreeDrive%\%WinDirectory%\system32\config\system",Run,%ScriptFile%,Halt_vdk,"ImageCopyFilesXP.cmd: copy files failed",ERROR

Which shoud mean that something has gone "beserk" with a previous step or with the VDK mounting, or, more probably, that there is a problem with the file ImageCopyFilesXP.cmd.

@cdob
Here is the drawback of enclosing a file inside a WB script and run it in a "hide" mode, final "newbie" user needs to ask for help for everything.

@shiggidy_
See if you can find the batch log file ImageCopyFilesXP.log and see what's in it.



Wonko

[shiggidy_]

Hi Wonko!

Which shoud mean that something has gone "beserk" with a previous step or with the VDK mounting, or, more probably, that there is a problem with the file ImageCopyFilesXP.cmd.

It is something with the ImageCopyFilesXP.cmd...in file manager I've seen the 4 (?) virtual drives for a short time (only for error-finding, the first starts were w/o filemanager) ... The script is permanent staying for ca. 3 seconds by showing 'ImageCopyFilesXP.cmd' and aborting w/o any error massage...

See if you can find the batch log file ImageCopyFilesXP.log and see what's in it.

The file is empty. There isn't more to find than 'copy files failed",ERROR'

[shiggidy_]

html.log

[Info] [//]
[Info] [// copy textmode boot files to mounted image]
[Success] ExtractFile - [ImageCopyFilesXP.cmd] to: [%BaseDir%\Temp\ChainBoot_XP]
[Info] execute ImageCopyFilesXP.cmd - read %BaseDir%\Temp\ChainBoot_XP\ImageCopyFilesXP.log
[Success] ShellExecute: [hide] using: [%BaseDir%\Temp\ChainBoot_XP\ImageCopyFilesXP.cmd] with parameters: ["I:\WINDOWS" Y: > "%BaseDir%\Temp\ChainBoot_XP\ImageCopyFilesXP.log"]
[Success] IF - File does not exist: [Y:\WINDOWS\system32\config\system] evaluated string: [If,NotExistFile,"%FreeDrive%\%WinDirectory%\system32\config\system",Run,%ScriptFile%,Halt_vdk,"ImageCopyFilesXP.cmd: copy files failed",ERROR]
Run - Processing section: [Halt_vdk] From file: [%BaseDir%\Projects\ChainbootXP\ChainBootXP.script]
[Parameter] with parameters: [ImageCopyFilesXP.cmd: copy files failed],[ERROR]
[Info] [// close image, remove vdk]
[Success] TxtAddLine - Added line: [%BaseDir%\Projects\Tools\vdk\vdk_WB.log] line: [***#$sremove] Option:"Append"
[Success] ShellExecute: [Hide] using: [cmd.exe] with parameters: [/c ""%BaseDir%\Projects\Tools\vdk\vdk_WB.exe" remove >> "%BaseDir%\Projects\Tools\vdk\vdk_WB.log""]
[Warning] ImageCopyFilesXP.cmd: copy files failed
Run - Processed section [Halt_vdk] in file: [%BaseDir%\Projects\ChainbootXP\ChainBootXP.script]
Run - Processed section [create-Chainboot-Image] in file: [%BaseDir%\Projects\ChainbootXP\ChainBootXP.script]
[Clock] Script time: 10 seconds and 953 miliseconds

[Done] Finished processing script: ChainBoot XP


[Clock] Project time: 11 seconds and 282 miliseconds

[Wonko the Sane]

We will need cdob to check the issue.

OT, but after all not that much

A new small batch:
http://www.boot-land...showtopic=10783


Wonko

[cdob]

ImageCopyFilesXP.log

The file is empty.

Which %BaseDir% directory do you use? Name the full path.
Attach the full log file.

Does exist files:

ChainbootXP\Temp\ChainBoot_XP\ChainBoot_open.cmd
ChainbootXP\Temp\ChainBoot_XP\ImageCopyFilesXP.cmd
ChainbootXP\Temp\ChainBoot_XP\ChainBoot_close.cmd

Does exist a drive Y: ?

Open the image: ChainBoot_open.cmd
Does exist a drive Y: now?

run: ImageCopyFilesXP.cmd "I:\WINDOWS" Y:
Do you get a error message?

Feel free to remark the first line at ImageCopyFilesXP.cmd:
rem @echo off

Close the image: ChainBoot_close.cmd

[shiggidy_]

Hallo cdob!

It was a problem with the target path...I put everyting to c:\ root now and it works...
BUT: This new error is strange:

copysgcs.exe "\\.\physicaldrive1" "C:\ChainBoot.img" 0x1B0
Error : failed read 512 byte from \\.\physicaldrive1.

=> Until now I've not found a piece of software that will read the mbr from ssd (sony sxs)...the only way is a hexeditor: The drive has a normal ntfs bootsector, I can confirm.
So maybe I've to copy the mbr manually to image? How can I do that?

[shiggidy_]

[cdob]

copysgcs.exe "\\.\physicaldrive1" "C:\ChainBoot.img" 0x1B0
Error : failed read 512 byte from \\.\physicaldrive1.

copysgcs use basic access to the drive: physicaldrive
That's a windows default solution to access a drive.

Does a protection software prohibit access to physicaldrive?
Which protection software do you use? Try disable the protection software.

the only way is a hexeditor

Run the hexeditor, save the MBR to a file mbr1.bin.

copysgcs.exe mbr1.bin C:\ChainBoot.img 0x1B0

[shiggidy_]

Hi cdob!

Which protection software do you use? Try disable the protection software.

No, there isn't any protection I know...

Run the hexeditor, save the MBR to a file mbr1.bin.

Done. File exact 512 bytes. I edited script:

Echo,"read MBR from %BootMBR%"
ExtractFile,"%ScriptFile%","Folder","copysgcs.exe","%ProjectTemp%"
FileCreateBlank,"%ProjectTemp%\copysgcs.log"
TxtAddLine,"%ProjectTemp%\copysgcs.log","copysgcs.exe mbr1.bin #$q%TargetDir%\ChainBoot.img#$q 0x1B0","append"
ShellExecute,hide,"cmd.exe","/c #$q#$q%ProjectTemp%\copysgcs.exe mbr1.bin #$q%TargetDir%\ChainBoot.img#$q 0x1B0 >>#$q%ProjectTemp%\copysgcs.log#$q#$q"
ShellExecute,hide,"findstr.exe","#$qError#$q #$q%ProjectTemp%\copysgcs.log#$q"

=> works.

Trying booting now with burned ISO...

[cdob]

No, there isn't any protection I know...

Do you use a virus scanner?
Can you access \\.\physicaldrive0. ?

Failed to copy [C:\ChainBoot.img] to: [C:\]

Why does exist a file C:\ChainBoot.img?

It was a problem with the target path...I put everyting to c:\ root now and it works...

Which target did you used before?
How did you put everyting to c:\ root?
You set target directory C:\. This creates a C:\ChainBoot.img.
Next copy fails C:\ChainBoot.img to c:\. Of course this fails, file exist already.

Do NOT set WinBuilder Target directory to c:\root. This is a internal temp directory.

Which root directory do you use?
Try move all to \ChainbootXP\.

What about the full log file?
What about \ChainbootXP\Temp\ChainBoot_XP\mkISO1.cmd ?
What about \ChainbootXP\Temp\ChainBoot_XP\mkisofs.log ?

[cdob]

No, there isn't any protection I know...

Do you use a virus scanner?
Can you access \\.\physicaldrive0. ?

Failed to copy [C:\ChainBoot.img] to: [C:\]

Why does exist a file C:\ChainBoot.img?

It was a problem with the target path...I put everyting to c:\ root now and it works...

Which target did you used before?
How did you put everyting to c:\ root?
You set target directory C:\. This creates a C:\ChainBoot.img.
Next copy fails C:\ChainBoot.img to c:\. Of course this fails, file exist already.

Do NOT set WinBuilder Target directory to c:\root. This is a internal temp directory.

Which root directory do you use?
Try move all to \ChainbootXP\.

What about the full log file?
What about \ChainbootXP\Temp\ChainBoot_XP\mkISO1.cmd ?
What about \ChainbootXP\Temp\ChainBoot_XP\mkisofs.log ?

[shiggidy_]

Do NOT set WinBuilder Target directory to c:\root. This is a internal temp directory.

Oh yeah, I recognized, sorry.

Do you use a virus scanner?

No.

Can you access \\.\physicaldrive0. ?

Yes, copysgcs.exe works there.

I installed to C:\ partition on local hdd now...on root there's only ChainBoot.img an MENU.LST > Grub is working (in installed it with Wingrub before).

GRUB: Booting 'ntldr ChainBoot Sony SXS' > local ntoskrnl.exe and hall.dll > BSOD 0x0000000007b
> removing SxS from pcie slot > booting winxp on old hdd

Tried also ACPI Uni/MultiProzessor PC, Standard PC, Advanced...(ACPI) PC, Safe mode boot

Any Idea what happens wrong?

[shiggidy_]

Update: Ok, I tried now the ISO-Version with the options
x) no options
y) - Add windows kernel and hal
- add firewire boot driver
- add pcmica boot driver
- reset USB driver config
- add some system boot settings

> The result is the same BSOD: PC has Virus or new Harddisk-Drive/ or and -Controller and you should remove them blahblah...$billions4bill$

> Interesting fact: Same BSOD if SXS removed but PCMCIA-Adapter with microdrive (from my digicam) is pluged...also remove him > xp is booting normal from old hdd partition > So maybe: the chainboot xp has a problem with any (?) additional harddrive in system > but fact: chainboot is looking AND finding other devices in booting up sequence

@all interested reader: I'm thinking about writing a tutorial (not only usable for the sxs) in the end if everything works

@cdob: I suppose your script is normally working and signature fake does it > so maybe I've to modify my cloned XP on the SxS (SSD) once more?

Many questions...I'm happy about answers!

[Wonko the Sane]

y) - Add windows kernel and hal
- add firewire boot driver
- add pcmica boot driver
- reset USB driver config
- add some system boot settings

If I may, most if not all of the above is either unneeded or irrelevant.

You want to boot from that stoopid sxs, adding firewire, pcmcia or USB bootability won't take you ANY nearer to this objective (and it may also "confuse" the issue)

As well, kernel has NOTHING to do with 0x0000007b, which is "unaccessible boot device".

Evidently something in the "original" install on SSD is NOT set properly (and consequently it is NOT set properly on the "XP Kansas City Shuffle image").

FORGET about ANY other bus, and re-check the settings for the "tree" where the SXS is connected.


Wonko

[shiggidy_]

Hi Wonko!

FORGET about ANY other bus, and re-check the settings for the "tree" where the SXS is connected.

I've done...there are two 'important' driver, pci.sys (Microsoft) and sxsmemcd.sys (Sony), both are set now to BootBusExtender, both copied correct ImageCopyFilesXP.log says. sxsmemcd.ico is also showed, must I put it in chainloader image to? if how? can a missing icon crash the system?

also used, but standard:
Volsnap.sys
Disk.sys
Partmgr.sys
pci.sys

Evidently something in the "original" install on SSD is NOT set properly (and consequently it is NOT set properly on the "XP Kansas City Shuffle image").

I made a complett new installation of XP on first normal hdd, first active partition w/o any protection etc...copysgcs.exe can't read the mbr of drive1 again, so I used this again:
copysgcs.exe mbr1.bin (made manually by hexedit 512 bytes) "c:\ChainbootXP\Target\ChainBoot_XP\ChainBoot.img" > cloned it to the sxs ssd > made iso > Same error.

Is the main problem not reading the mbr from sxs (in booting sequence), one kind of hard coded protection by sony?

[shiggidy_]

Update: I integrated the sxsmemcd.ico into chainloader image > burned iso > same BSOD!

So I think it's a problem with the mbr of the sxs, right? windows cannot read it, maybe a protection???

[shiggidy_]

ImageCopyFilesXP.log

C:\NTDETECT.COM -> Z:\NTDETECT.COM
1 Datei(en) kopiert
C:\ntldr -> Z:\ntldr
1 Datei(en) kopiert
C:\Bootfont.bin
0 Datei(en) kopiert.
0 Datei(en) kopiert
G:\Windows\FONTS\vga850.fon -> Z:\Windows\FONTS\vga850.fon
1 Datei(en) kopiert
G:\Windows\INF\biosinfo.inf -> Z:\Windows\INF\biosinfo.inf
1 Datei(en) kopiert
G:\Windows\system32\ntoskrnl.exe -> Z:\Windows\system32\ntoskrnl.exe
1 Datei(en) kopiert
G:\Windows\system32\hal.dll -> Z:\Windows\system32\hal.dll
1 Datei(en) kopiert
G:\Windows\system32\bootvid.dll -> Z:\Windows\system32\bootvid.dll
1 Datei(en) kopiert
G:\Windows\system32\c_1252.nls -> Z:\Windows\system32\c_1252.nls
1 Datei(en) kopiert
G:\Windows\system32\c_850.nls -> Z:\Windows\system32\c_850.nls
1 Datei(en) kopiert
G:\Windows\system32\kdcom.dll -> Z:\Windows\system32\kdcom.dll
1 Datei(en) kopiert
G:\Windows\system32\l_intl.nls -> Z:\Windows\system32\l_intl.nls
1 Datei(en) kopiert
G:\Windows\system32\config\system -> Z:\Windows\system32\config\system
1 Datei(en) kopiert

load registry file "Z:\Windows\system32\config\system"

Der Vorgang wurde erfolgreich ausgeführt.


ControlSet "ControlSet001" used.
G:\Windows\system32\drivers\acpi.sys -> Z:\Windows\system32\drivers\acpi.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\acpiec.sys -> Z:\Windows\system32\drivers\acpiec.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\atapi.sys -> Z:\Windows\system32\drivers\atapi.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\compbatt.sys -> Z:\Windows\system32\drivers\compbatt.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\disk.sys -> Z:\Windows\system32\drivers\disk.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\fltMgr.sys -> Z:\Windows\system32\drivers\fltMgr.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\ftdisk.sys -> Z:\Windows\system32\drivers\ftdisk.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\isapnp.sys -> Z:\Windows\system32\drivers\isapnp.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\ksecdd.sys -> Z:\Windows\system32\drivers\ksecdd.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\mountmgr.sys -> Z:\Windows\system32\drivers\mountmgr.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\mup.sys -> Z:\Windows\system32\drivers\mup.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\ndis.sys -> Z:\Windows\system32\drivers\ndis.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\partmgr.sys -> Z:\Windows\system32\drivers\partmgr.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\pci.sys -> Z:\Windows\system32\drivers\pci.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\pciide.sys -> Z:\Windows\system32\drivers\pciide.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\pcmcia.sys -> Z:\Windows\system32\drivers\pcmcia.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\sr.sys -> Z:\Windows\system32\drivers\sr.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\SxSmemcd.sys -> Z:\Windows\system32\drivers\SxSmemcd.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\volsnap.sys -> Z:\Windows\system32\drivers\volsnap.sys
1 Datei(en) kopiert

unload registry HKLM\loaded_SYSTEM

Der Vorgang wurde erfolgreich ausgeführt.

G:\Windows\system32\drivers\fastfat.sys -> Z:\Windows\system32\drivers\fastfat.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\classpnp.sys -> Z:\Windows\system32\drivers\classpnp.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\wmilib.sys -> Z:\Windows\system32\drivers\wmilib.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\scsiport.sys -> Z:\Windows\system32\drivers\scsiport.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\pciidex.sys -> Z:\Windows\system32\drivers\pciidex.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\oprghdlr.sys -> Z:\Windows\system32\drivers\oprghdlr.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\battc.sys -> Z:\Windows\system32\drivers\battc.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\usbehci.sys -> Z:\Windows\system32\drivers\usbehci.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\usbuhci.sys -> Z:\Windows\system32\drivers\usbuhci.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\usbport.sys -> Z:\Windows\system32\drivers\usbport.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\usbhub.sys -> Z:\Windows\system32\drivers\usbhub.sys
1 Datei(en) kopiert
G:\Windows\system32\drivers\usbd.sys -> Z:\Windows\system32\drivers\usbd.sys

[shiggidy_]

Ok, I thing I know what's the problem: the stupid sxs has a sector size of 2048 bytes, all my other drives (usb etc.) has 512 bytes per sector. So maybe that's the problem for not direct accessing, reading/writing mbr and so on...

[Wonko the Sane]

Ok, I thing I know what's the problem: the stupid sxs has a sector size of 2048 bytes, all my other drives (usb etc.) has 512 bytes per sector. So maybe that's the problem for not direct accessing, reading/writing mbr and so on...

That's a possibility.

But I wouldn't be that sure.

Can you try a dsfo like this:

dsfo \\.\Physicaldriven 0 2048 C:\first2048.bin

You do know which \\.\Physicaldrive number the sxs gets, don't you?


Wonko

[shiggidy_]

Hi Wonko!

Can you try a dsfo like this

dsfo \\.\Physicaldrive0 0 2048 C:\first2048.bin > that works and its exactly the same content winhex shows by opening the sxs at sector 0.
There are two drives inside the thinkpad for now: SxS and ToshibaHDD. dsfo works with Physicaldrive0 AND Physicaldrive1 !!!

You do know which \\.\Physicaldrive number the sxs gets, don't you?

Yes, I always look with run 'compmgmt.msc'.... hard drive managing.

So could this be the problem not reading mbr? I looked for low level formating tool to set sector size at sxs to 512...not find a working tool...

[Wonko the Sane]

dsfo \\.\Physicaldrive0 0 2048 C:\first2048.bin > that works and its exactly the same content winhex shows by opening the sxs at sector 0.

And what happens if you do:

dsfo \\.\Physicaldriven 0 512 C:\first512.bin

Yes, I always look with run 'compmgmt.msc'.... hard drive managing.

The only thing I can be sure about from a distance is that it CANNOT be:

dsfo \\.\Physicaldrive0 0 2048 C:\first2048.bin > that works and its exactly the same content winhex shows by opening the sxs at sector 0.

as drive 0 is BOOT drive, so you either have a wrong drive n or you already booted from the sxs

So could this be the problem not reading mbr?

Cannot say, but as said I instinctively doubt it.


Wonko

[shiggidy_]

And what happens if you do:

dsfo \\.\Physicaldrive0 0 512 C:\first512.bin
dsfo \\.\Physicaldrive1 0 512 C:\first512_2.bin
> also works on both drives...

dsfo \\.\Physicaldrive2 0 512 C:\first512_3.bin > error, system couldn't find drive cause there is no one

The only thing I can be sure about from a distance is that it CANNOT be:
as drive 0 is BOOT drive, so you either have a wrong drive n or you already booted from the sxs

> with installed low filter driver (hitachi microdrive) I could set up the sxs creating create a partition on it, format to ntfs AND set active (boot). wrong? the filter driver is NOT on the chainboot image...

[Wonko the Sane]

Let's start again.

When a machine boots, the machine's BIOS assigns a number to drives.
Usually when a Windows boots it keeps the same drive numbering.

\\.\Physicaldrive0 means FIRST disk and it is usually the boot device, i.e. first device.

Now that you have BOTH:

• C:\first512.bin
  
• C:\first512_2.bin

can you take the SXS out, reboot and run:

dsfo \\.\Physicaldrive0 0 512 C:\first512_0.bin

Now compare C:\first512_0.bin with C:\first512.bin (are they the same)?
Now compare C:\first512_0.bin with C:\first512_2.bin (are they the same)?


Wonko

[cdob]

sxs has a sector size of 2048 bytes

Does windows calculate checksum at first 512 bytes or first sector (512 bytes at most drives and 2048 bytes at sxs card)?

Let's calculate sxs card at virtual 512 byte sectors. First virtual 512 byte sector contain the MBR.
Can you copy virtual sectors 2 to 4 to fake boot image file?