missing hal.dll again

[Johannes Stratmann]

I get the famous 'missing hal.dll' message on computer start: the disk
contains two primary partitions, C: is 35 GB and D: is 250 GB large. I made
an image with drive settings = D: and the boot.ini is:

[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XPe"
/fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XPe C"
/fastdetect /noexecute=AlwaysOff

Booting from the 2nd partitions D: works fine (system partition is C: and
boot.ini is there). Now I want to use the same image on Drive C: and I
changed the drive settings to C: and I use the 2nd entry in boot.ini. But
this gives always the 'hal.dll missing' error. The only idea I still have is
that it is a problem with the large drive. But I would expect the problem
then on the 2nd, the larger partition.

Any ideas?



The partition info from PartitionMagic:

General System Information:
Total Physical Memory (bytes): 1,006,092,288
Used Physical Memory: (bytes): 335,036,416
Maximum Page File Size: (bytes): 920,465,408
Current Page File Size: (bytes): 242,761,728



===========================================================================================================
Disk Geometry Information for Disk 1: 36483 Cylinders, 255 Heads, 63
Sectors/Track
System PartSect # Boot BCyl Head Sect FS ECyl Head Sect
StartSect NumSects
===========================================================================================================
0 0 80 0 1 1 07 1023 254 63
63 72,710,127
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 0 80 0 1 1 07 4525 254 63 63 72710127
0 1 00 1023 0 1 07 1023 254 63
72,710,190 513,389,205
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 1 00 4526 0 1 07 36482 254 63 72710190 513389205



===========================================================================================================
Partition Information for Disk 1: 286,181.3 Megabytes
Volume PartType Status Size MB PartSect # StartSect
TotalSects
===========================================================================================================
C: NTFS Pri,Boot 35,503.0 0 0 63
72,710,127
D: NTFS Pri 250,678.3 0 1 72,710,190
513,389,205


===========================================================================================================
Boot Record for drive C: (Drive: 1, Starting sector: 63, Type: NTFS)
===========================================================================================================
1. Jump: EB 52 90
2. OEM Name: NTFS
3. Bytes per Sector: 512
4. Sectors per Cluster: 8
5. Reserved Sectors: 0
6. Number of FATs: 0
7. Root Dir Entries: 0
8. Total Sectors: 0
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 63 (0x3F)
14. Total Sectors (>32MB): 0 (0x0)
15. Unused: 0x80008000
16. Total NTFS Sectors: 72710126
17. MFT Start Cluster: 4
18. MFT Mirror Start Clust: 4883756
19. Clusters per FRS: 246
20. Clusters per Index Blk: 1
21. Serial Number: 0x0000000043B00C17
22. Checksum: 0 (0x0)
23. Boot Signature: 0xAA55

===========================================================================================================
Boot Record for drive D: (Drive: 1, Starting sector: 72,710,190, Type:
NTFS)
===========================================================================================================
1. Jump: EB 5B 90
2. OEM Name: NTFS
3. Bytes per Sector: 512
4. Sectors per Cluster: 8
5. Reserved Sectors: 0
6. Number of FATs: 0
7. Root Dir Entries: 0
8. Total Sectors: 0
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 72710190 (0x455782E)
14. Total Sectors (>32MB): 0 (0x0)
15. Unused: 0x80008000
16. Total NTFS Sectors: 513389204
17. MFT Start Cluster: 4
18. MFT Mirror Start Clust: 340374
19. Clusters per FRS: 246
20. Clusters per Index Blk: 1
21. Serial Number: 0x00000000876019DA
22. Checksum: 0 (0x0)
23. Boot Signature: 0xAA55

 

[Sean Liming \(eMVP\)]

What did you format the drive in FAT or NTFS? And do you have the same file
system support in the image?


Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit

I get the famous 'missing hal.dll' message on computer start: the disk
contains two primary partitions, C: is 35 GB and D: is 250 GB large. I made
an image with drive settings = D: and the boot.ini is:

[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XPe"
/fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XPe C"
/fastdetect /noexecute=AlwaysOff

Booting from the 2nd partitions D: works fine (system partition is C: and
boot.ini is there). Now I want to use the same image on Drive C: and I
changed the drive settings to C: and I use the 2nd entry in boot.ini. But
this gives always the 'hal.dll missing' error. The only idea I still have
is that it is a problem with the large drive. But I would expect the
problem then on the 2nd, the larger partition.

Any ideas?



The partition info from PartitionMagic:

General System Information:
Total Physical Memory (bytes): 1,006,092,288
Used Physical Memory: (bytes): 335,036,416
Maximum Page File Size: (bytes): 920,465,408
Current Page File Size: (bytes): 242,761,728



===========================================================================================================
Disk Geometry Information for Disk 1: 36483 Cylinders, 255 Heads, 63
Sectors/Track
System PartSect # Boot BCyl Head Sect FS ECyl Head Sect
StartSect NumSects
===========================================================================================================
0 0 80 0 1 1 07 1023 254 63
63 72,710,127
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 0 80 0 1 1 07 4525 254 63 63 72710127
0 1 00 1023 0 1 07 1023 254 63
72,710,190 513,389,205
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 1 00 4526 0 1 07 36482 254 63 72710190 513389205



===========================================================================================================
Partition Information for Disk 1: 286,181.3 Megabytes
Volume PartType Status Size MB PartSect # StartSect
TotalSects
===========================================================================================================
C: NTFS Pri,Boot 35,503.0 0 0 63
72,710,127
D: NTFS Pri 250,678.3 0 1 72,710,190
513,389,205


===========================================================================================================
Boot Record for drive C: (Drive: 1, Starting sector: 63, Type: NTFS)
===========================================================================================================
1. Jump: EB 52 90
2. OEM Name: NTFS
3. Bytes per Sector: 512
4. Sectors per Cluster: 8
5. Reserved Sectors: 0
6. Number of FATs: 0
7. Root Dir Entries: 0
8. Total Sectors: 0
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 63 (0x3F)
14. Total Sectors (>32MB): 0 (0x0)
15. Unused: 0x80008000
16. Total NTFS Sectors: 72710126
17. MFT Start Cluster: 4
18. MFT Mirror Start Clust: 4883756
19. Clusters per FRS: 246
20. Clusters per Index Blk: 1
21. Serial Number: 0x0000000043B00C17
22. Checksum: 0 (0x0)
23. Boot Signature: 0xAA55

===========================================================================================================
Boot Record for drive D: (Drive: 1, Starting sector: 72,710,190, Type:
NTFS)
===========================================================================================================
1. Jump: EB 5B 90
2. OEM Name: NTFS
3. Bytes per Sector: 512
4. Sectors per Cluster: 8
5. Reserved Sectors: 0
6. Number of FATs: 0
7. Root Dir Entries: 0
8. Total Sectors: 0
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 72710190 (0x455782E)
14. Total Sectors (>32MB): 0 (0x0)
15. Unused: 0x80008000
16. Total NTFS Sectors: 513389204
17. MFT Start Cluster: 4
18. MFT Mirror Start Clust: 340374
19. Clusters per FRS: 246
20. Clusters per Index Blk: 1
21. Serial Number: 0x00000000876019DA
22. Checksum: 0 (0x0)
23. Boot Signature: 0xAA55

 

[Johannes Stratmann]

the FS is NTFS for both partitions and the support is included in the image.
The C: drive is ok, I can access it when I boot from the XPe on drive D:.

 

[Johannes Stratmann]

I have checked the NTLDR Version and found that the component Version
5.1.2600.3333 should be used with a file size of 251904 Bytes. But I cannot
find this ntldr version in my repository, in the image I find a version from
SP2. I will try now to reinstall the 2008 Rollup.

 

[Johannes Stratmann]

seems also to be the wrong way, the ntldr source file size is rounded to
1024 Bytes. So the ntldr from 2004 should be ok.

 

[Guest]

Johannes,

You have two XPe images?

Let's look at the image for the 2nd partition.
In TD, you should setup your details like this

(Bear with me I'm not at my dev machine)

Boot Drive:
C:
System:
D:\WINDOWS
Documents and Settings:
D:\Documents and Settings
Program Files:
D:\Program Files

When you image is built. A folder called "DriveD" is created. You'll need to
pluck out the 3 folders in the "DriveD" folder and place it in the root of
your 2nd partition, as well as the rest of the files along side, so you have
all the files where they should be.

Now you can boot to your 2nd partition. ( Assuming that you have a corrected
boot.ini file )

As for your first partition, it's just the default settings in TD. (
everything starting from C: )


Your boot.ini should be

[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XPe"
/fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XPe C"
/fastdetect /noexecute=AlwaysOff

Hope my memory serves me correctly here, other wise I look silly.

I get the famous 'missing hal.dll' message on computer start: the disk
contains two primary partitions, C: is 35 GB and D: is 250 GB large. I made
an image with drive settings = D: and the boot.ini is:

[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XPe"
/fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XPe C"
/fastdetect /noexecute=AlwaysOff

Booting from the 2nd partitions D: works fine (system partition is C: and
boot.ini is there). Now I want to use the same image on Drive C: and I
changed the drive settings to C: and I use the 2nd entry in boot.ini. But
this gives always the 'hal.dll missing' error. The only idea I still have is
that it is a problem with the large drive. But I would expect the problem
then on the 2nd, the larger partition.

Any ideas?



The partition info from PartitionMagic:

General System Information:
Total Physical Memory (bytes): 1,006,092,288
Used Physical Memory: (bytes): 335,036,416
Maximum Page File Size: (bytes): 920,465,408
Current Page File Size: (bytes): 242,761,728



===========================================================================================================
Disk Geometry Information for Disk 1: 36483 Cylinders, 255 Heads, 63
Sectors/Track
System PartSect # Boot BCyl Head Sect FS ECyl Head Sect
StartSect NumSects
===========================================================================================================
0 0 80 0 1 1 07 1023 254 63
63 72,710,127
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 0 80 0 1 1 07 4525 254 63 63 72710127
0 1 00 1023 0 1 07 1023 254 63
72,710,190 513,389,205
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 1 00 4526 0 1 07 36482 254 63 72710190 513389205



===========================================================================================================
Partition Information for Disk 1: 286,181.3 Megabytes
Volume PartType Status Size MB PartSect # StartSect
TotalSects
===========================================================================================================
C: NTFS Pri,Boot 35,503.0 0 0 63
72,710,127
D: NTFS Pri 250,678.3 0 1 72,710,190
513,389,205


===========================================================================================================
Boot Record for drive C: (Drive: 1, Starting sector: 63, Type: NTFS)
===========================================================================================================
1. Jump: EB 52 90
2. OEM Name: NTFS
3. Bytes per Sector: 512
4. Sectors per Cluster: 8
5. Reserved Sectors: 0
6. Number of FATs: 0
7. Root Dir Entries: 0
8. Total Sectors: 0
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 63 (0x3F)
14. Total Sectors (>32MB): 0 (0x0)
15. Unused: 0x80008000
16. Total NTFS Sectors: 72710126
17. MFT Start Cluster: 4
18. MFT Mirror Start Clust: 4883756
19. Clusters per FRS: 246
20. Clusters per Index Blk: 1
21. Serial Number: 0x0000000043B00C17
22. Checksum: 0 (0x0)
23. Boot Signature: 0xAA55

===========================================================================================================
Boot Record for drive D: (Drive: 1, Starting sector: 72,710,190, Type:
NTFS)
===========================================================================================================
1. Jump: EB 5B 90
2. OEM Name: NTFS
3. Bytes per Sector: 512
4. Sectors per Cluster: 8
5. Reserved Sectors: 0
6. Number of FATs: 0
7. Root Dir Entries: 0
8. Total Sectors: 0
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 72710190 (0x455782E)
14. Total Sectors (>32MB): 0 (0x0)
15. Unused: 0x80008000
16. Total NTFS Sectors: 513389204
17. MFT Start Cluster: 4
18. MFT Mirror Start Clust: 340374
19. Clusters per FRS: 246
20. Clusters per Index Blk: 1
21. Serial Number: 0x00000000876019DA
22. Checksum: 0 (0x0)
23. Boot Signature: 0xAA55

 

[Guest]

Well, I look silly 'cause I didn't read the post completely.

The boot.ini in the 2nd partition is not important, however, it's
recommended to leave it there.

Sounds like you've wanted to make changes *after* you have built the images.
It's important to build the images with the desired settings, otherwise FBA
won't be able to process completely.
Ie: Keeps looking in the wrong locations for things that were set in TD.
Say, if you build an image to boot from a third partition, and then you
change the partition number in the boot.ini file, the system may start and
begin the FBA process. What happens then is FBA is going to expect everything
to be in the third partition.

Please pull me up if I've got it all wrong.

Johannes,

You have two XPe images?

Let's look at the image for the 2nd partition.
In TD, you should setup your details like this

(Bear with me I'm not at my dev machine)

Boot Drive:
C:
System:
D:\WINDOWS
Documents and Settings:
D:\Documents and Settings
Program Files:
D:\Program Files

When you image is built. A folder called "DriveD" is created. You'll need to
pluck out the 3 folders in the "DriveD" folder and place it in the root of
your 2nd partition, as well as the rest of the files along side, so you have
all the files where they should be.

Now you can boot to your 2nd partition. ( Assuming that you have a corrected
boot.ini file )

As for your first partition, it's just the default settings in TD. (
everything starting from C: )


Your boot.ini should be

[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XPe"
/fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XPe C"
/fastdetect /noexecute=AlwaysOff

Hope my memory serves me correctly here, other wise I look silly.

I get the famous 'missing hal.dll' message on computer start: the disk
contains two primary partitions, C: is 35 GB and D: is 250 GB large. I made
an image with drive settings = D: and the boot.ini is:

[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XPe"
/fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XPe C"
/fastdetect /noexecute=AlwaysOff

Booting from the 2nd partitions D: works fine (system partition is C: and
boot.ini is there). Now I want to use the same image on Drive C: and I
changed the drive settings to C: and I use the 2nd entry in boot.ini. But
this gives always the 'hal.dll missing' error. The only idea I still have is
that it is a problem with the large drive. But I would expect the problem
then on the 2nd, the larger partition.

Any ideas?



The partition info from PartitionMagic:

General System Information:
Total Physical Memory (bytes): 1,006,092,288
Used Physical Memory: (bytes): 335,036,416
Maximum Page File Size: (bytes): 920,465,408
Current Page File Size: (bytes): 242,761,728



===========================================================================================================
Disk Geometry Information for Disk 1: 36483 Cylinders, 255 Heads, 63
Sectors/Track
System PartSect # Boot BCyl Head Sect FS ECyl Head Sect
StartSect NumSects
===========================================================================================================
0 0 80 0 1 1 07 1023 254 63
63 72,710,127
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 0 80 0 1 1 07 4525 254 63 63 72710127
0 1 00 1023 0 1 07 1023 254 63
72,710,190 513,389,205
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 1 00 4526 0 1 07 36482 254 63 72710190 513389205



===========================================================================================================
Partition Information for Disk 1: 286,181.3 Megabytes
Volume PartType Status Size MB PartSect # StartSect
TotalSects
===========================================================================================================
C: NTFS Pri,Boot 35,503.0 0 0 63
72,710,127
D: NTFS Pri 250,678.3 0 1 72,710,190
513,389,205


===========================================================================================================
Boot Record for drive C: (Drive: 1, Starting sector: 63, Type: NTFS)
===========================================================================================================
1. Jump: EB 52 90
2. OEM Name: NTFS
3. Bytes per Sector: 512
4. Sectors per Cluster: 8
5. Reserved Sectors: 0
6. Number of FATs: 0
7. Root Dir Entries: 0
8. Total Sectors: 0
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 63 (0x3F)
14. Total Sectors (>32MB): 0 (0x0)
15. Unused: 0x80008000
16. Total NTFS Sectors: 72710126
17. MFT Start Cluster: 4
18. MFT Mirror Start Clust: 4883756
19. Clusters per FRS: 246
20. Clusters per Index Blk: 1
21. Serial Number: 0x0000000043B00C17
22. Checksum: 0 (0x0)
23. Boot Signature: 0xAA55

===========================================================================================================
Boot Record for drive D: (Drive: 1, Starting sector: 72,710,190, Type:
NTFS)
===========================================================================================================
1. Jump: EB 5B 90
2. OEM Name: NTFS
3. Bytes per Sector: 512
4. Sectors per Cluster: 8
5. Reserved Sectors: 0
6. Number of FATs: 0
7. Root Dir Entries: 0
8. Total Sectors: 0
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 72710190 (0x455782E)
14. Total Sectors (>32MB): 0 (0x0)
15. Unused: 0x80008000
16. Total NTFS Sectors: 513389204
17. MFT Start Cluster: 4
18. MFT Mirror Start Clust: 340374
19. Clusters per FRS: 246
20. Clusters per Index Blk: 1
21. Serial Number: 0x00000000876019DA
22. Checksum: 0 (0x0)
23. Boot Signature: 0xAA55

 

[Martin Grossen, eMVP [AVNET Silica]]

Johannes

You can not use the same image from D: on C:.
Remember, that you have to enter the pathes in Target Designer.
(Target Device Settings)

Go back and build your image for the C: drive there.


--

Martin Grossen, eMVP

AVNET EMG Silica
Franchise Manager Microsoft Embedded Europe

Your competent partner for Microsoft Embedded licencing

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I get the famous 'missing hal.dll' message on computer start: the disk
contains two primary partitions, C: is 35 GB and D: is 250 GB large. I made
an image with drive settings = D: and the boot.ini is:

[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XPe"
/fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XPe C"
/fastdetect /noexecute=AlwaysOff

Booting from the 2nd partitions D: works fine (system partition is C: and
boot.ini is there). Now I want to use the same image on Drive C: and I
changed the drive settings to C: and I use the 2nd entry in boot.ini. But
this gives always the 'hal.dll missing' error. The only idea I still have
is that it is a problem with the large drive. But I would expect the
problem then on the 2nd, the larger partition.

Any ideas?



The partition info from PartitionMagic:

General System Information:
Total Physical Memory (bytes): 1,006,092,288
Used Physical Memory: (bytes): 335,036,416
Maximum Page File Size: (bytes): 920,465,408
Current Page File Size: (bytes): 242,761,728



===========================================================================================================
Disk Geometry Information for Disk 1: 36483 Cylinders, 255 Heads, 63
Sectors/Track
System PartSect # Boot BCyl Head Sect FS ECyl Head Sect
StartSect NumSects
===========================================================================================================
0 0 80 0 1 1 07 1023 254 63
63 72,710,127
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 0 80 0 1 1 07 4525 254 63 63 72710127
0 1 00 1023 0 1 07 1023 254 63
72,710,190 513,389,205
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 1 00 4526 0 1 07 36482 254 63 72710190 513389205



===========================================================================================================
Partition Information for Disk 1: 286,181.3 Megabytes
Volume PartType Status Size MB PartSect # StartSect
TotalSects
===========================================================================================================
C: NTFS Pri,Boot 35,503.0 0 0 63
72,710,127
D: NTFS Pri 250,678.3 0 1 72,710,190
513,389,205


===========================================================================================================
Boot Record for drive C: (Drive: 1, Starting sector: 63, Type: NTFS)
===========================================================================================================
1. Jump: EB 52 90
2. OEM Name: NTFS
3. Bytes per Sector: 512
4. Sectors per Cluster: 8
5. Reserved Sectors: 0
6. Number of FATs: 0
7. Root Dir Entries: 0
8. Total Sectors: 0
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 63 (0x3F)
14. Total Sectors (>32MB): 0 (0x0)
15. Unused: 0x80008000
16. Total NTFS Sectors: 72710126
17. MFT Start Cluster: 4
18. MFT Mirror Start Clust: 4883756
19. Clusters per FRS: 246
20. Clusters per Index Blk: 1
21. Serial Number: 0x0000000043B00C17
22. Checksum: 0 (0x0)
23. Boot Signature: 0xAA55

===========================================================================================================
Boot Record for drive D: (Drive: 1, Starting sector: 72,710,190, Type:
NTFS)
===========================================================================================================
1. Jump: EB 5B 90
2. OEM Name: NTFS
3. Bytes per Sector: 512
4. Sectors per Cluster: 8
5. Reserved Sectors: 0
6. Number of FATs: 0
7. Root Dir Entries: 0
8. Total Sectors: 0
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 72710190 (0x455782E)
14. Total Sectors (>32MB): 0 (0x0)
15. Unused: 0x80008000
16. Total NTFS Sectors: 513389204
17. MFT Start Cluster: 4
18. MFT Mirror Start Clust: 340374
19. Clusters per FRS: 246
20. Clusters per Index Blk: 1
21. Serial Number: 0x00000000876019DA
22. Checksum: 0 (0x0)
23. Boot Signature: 0xAA55

 

[Martin Grossen, eMVP [AVNET Silica]]

Some other hints:

- make sure, the partition C: is partitioned as primary.
- make sure, the Windows subdirectory is on the C: drive and not another
name.


--

Martin Grossen, eMVP

AVNET EMG Silica
Franchise Manager Microsoft Embedded Europe

Your competent partner for Microsoft Embedded licencing

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I get the famous 'missing hal.dll' message on computer start: the disk
contains two primary partitions, C: is 35 GB and D: is 250 GB large. I made
an image with drive settings = D: and the boot.ini is:

[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XPe"
/fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XPe C"
/fastdetect /noexecute=AlwaysOff

Booting from the 2nd partitions D: works fine (system partition is C: and
boot.ini is there). Now I want to use the same image on Drive C: and I
changed the drive settings to C: and I use the 2nd entry in boot.ini. But
this gives always the 'hal.dll missing' error. The only idea I still have
is that it is a problem with the large drive. But I would expect the
problem then on the 2nd, the larger partition.

Any ideas?



The partition info from PartitionMagic:

General System Information:
Total Physical Memory (bytes): 1,006,092,288
Used Physical Memory: (bytes): 335,036,416
Maximum Page File Size: (bytes): 920,465,408
Current Page File Size: (bytes): 242,761,728



===========================================================================================================
Disk Geometry Information for Disk 1: 36483 Cylinders, 255 Heads, 63
Sectors/Track
System PartSect # Boot BCyl Head Sect FS ECyl Head Sect
StartSect NumSects
===========================================================================================================
0 0 80 0 1 1 07 1023 254 63
63 72,710,127
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 0 80 0 1 1 07 4525 254 63 63 72710127
0 1 00 1023 0 1 07 1023 254 63
72,710,190 513,389,205
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 1 00 4526 0 1 07 36482 254 63 72710190 513389205



===========================================================================================================
Partition Information for Disk 1: 286,181.3 Megabytes
Volume PartType Status Size MB PartSect # StartSect
TotalSects
===========================================================================================================
C: NTFS Pri,Boot 35,503.0 0 0 63
72,710,127
D: NTFS Pri 250,678.3 0 1 72,710,190
513,389,205


===========================================================================================================
Boot Record for drive C: (Drive: 1, Starting sector: 63, Type: NTFS)
===========================================================================================================
1. Jump: EB 52 90
2. OEM Name: NTFS
3. Bytes per Sector: 512
4. Sectors per Cluster: 8
5. Reserved Sectors: 0
6. Number of FATs: 0
7. Root Dir Entries: 0
8. Total Sectors: 0
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 63 (0x3F)
14. Total Sectors (>32MB): 0 (0x0)
15. Unused: 0x80008000
16. Total NTFS Sectors: 72710126
17. MFT Start Cluster: 4
18. MFT Mirror Start Clust: 4883756
19. Clusters per FRS: 246
20. Clusters per Index Blk: 1
21. Serial Number: 0x0000000043B00C17
22. Checksum: 0 (0x0)
23. Boot Signature: 0xAA55

===========================================================================================================
Boot Record for drive D: (Drive: 1, Starting sector: 72,710,190, Type:
NTFS)
===========================================================================================================
1. Jump: EB 5B 90
2. OEM Name: NTFS
3. Bytes per Sector: 512
4. Sectors per Cluster: 8
5. Reserved Sectors: 0
6. Number of FATs: 0
7. Root Dir Entries: 0
8. Total Sectors: 0
9. Media Descriptor: 0xF8
10. Sectors per FAT: 0
11. Sectors per Track: 63 (0x3F)
12. Number of Heads: 255 (0xFF)
13. Hidden Sectors: 72710190 (0x455782E)
14. Total Sectors (>32MB): 0 (0x0)
15. Unused: 0x80008000
16. Total NTFS Sectors: 513389204
17. MFT Start Cluster: 4
18. MFT Mirror Start Clust: 340374
19. Clusters per FRS: 246
20. Clusters per Index Blk: 1
21. Serial Number: 0x00000000876019DA
22. Checksum: 0 (0x0)
23. Boot Signature: 0xAA55

 

[Johannes Stratmann]

this is the case, C: primary NTFS, D: primary NTFS, subdir names are
standard.
The images for c: and d: are not the same, the drive letters are adjusted.
But even when the drive letter settings in the image are wrong you typically
get the 'always rebooting' loop in the FBA, but not 'missing hal.dll'.

I'll try now with another HD, a smaller one.

 

[Johannes Stratmann]

thanks for your ideas,
I've built already several images but this hardware drives me nuts... I
build it for a home settop box and C: should be the smaller boot, D: for
data. But this did not work from the beginning and I got the system running
only on the 2nd partition.
Now I did a revamp and used the FP2007 updates, but with the same results. I
try it now again with a smaller (40GB) HD, my suspect is the large HD.

 

[Johannes Stratmann]

now with the 40gib hd the same image works on c:. So there must be something
wrong with the c-partition on the large drive, I think I need to re-format
it.

 

[Guest]

You haven't heard? Size doesn't matter. You can use the Seagate One
Terrabyte and it wouldn't matter.

 

[Johannes Stratmann]

yes, you're right. I got my problem solved: after re-formatting the c drive
my image booted correctly.