MSFN Forum: Hal.dll error - It just can't find the WINDOWS folder. - MSFN Forum

Jump to content



Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Hal.dll error - It just can't find the WINDOWS folder.

#1 User is offline   warlock554 

  • Group: Members
  • Posts: 5
  • Joined: 03-November 08

Posted 03 November 2008 - 09:21 AM

Since my CD-ROM seems to be malfunctioning, I've made a bootable USB using the USB Multiboot 10 tool and an unattended XP version. After completing the txt install and attempting to continue with the GUI part of the setup, I get a 'corrupt or missing hal.dll' error. I tried everything: using just one partition, fixing the mbr, fixing the boot.ini, but without any success. There's no hardware issue as I can install linux just fine.

Please help. :ph34r: :)

This post has been edited by warlock554: 07 November 2008 - 12:48 PM



#2 User is offline   Ponch 

  • MSFN Master
  • Group: Patrons
  • Posts: 2,715
  • Joined: 23-November 05
  • OS:none specified
  • Country: Country Flag

Posted 03 November 2008 - 05:22 PM

What's your partitions setup and to which one are you installing ? Is there any hidden partition ?

#3 User is offline   warlock554 

  • Group: Members
  • Posts: 5
  • Joined: 03-November 08

Posted 05 November 2008 - 01:51 PM

I first tried a 2 partition configuration and installed XP on the first one. I also tried having just one partition. No hidden partitions. In both cases I got the same result.

#4 User is offline   wimb 

  • Senior Member
  • Group: Developers
  • Posts: 575
  • Joined: 21-March 07

Posted 06 November 2008 - 02:03 AM

The message system32\hal.dll missing means only that the WINDOWS folder cannot be found,
and is NOT on the drive where it was expected. There is no missing file in this case.
It is necessary to Boot all the time from the USB-drive and keep it connected until Logon.
Change your BIOS Boot Priority such that USB-stick is seen as First Harddisk.

Read Also FAQ-4 http://www.msfn.org/...Qs-t116766.html

This post has been edited by wimb: 06 November 2008 - 02:06 AM


#5 User is offline   warlock554 

  • Group: Members
  • Posts: 5
  • Joined: 03-November 08

Posted 07 November 2008 - 05:24 AM

Boot.ini points to HD 1. I set my second boot device to HD 1 (the USB being the first), tried again, but got the same error. :blink:
Tried again with a different version and different installer. No luck...

This post has been edited by warlock554: 07 November 2008 - 07:17 AM


#6 User is offline   ilko_t 

  • MSFN Expert
  • Group: Super Moderator
  • Posts: 1,458
  • Joined: 06-December 06
  • OS:none specified
  • Country: Country Flag

Posted 07 November 2008 - 12:49 PM

warlock554, you need to read carefully FAQ #4.
If you did so, you should have posted your partition number as well, which is as important as the harddisk number. Windows folder matters as well.
There is no point to use different installers etc.

Better take a picture of this screen:
Posted Image

Does partitionN match what you have in boot.ini on USB disk?
In this example Windows was installed to partition2. Partition(1) is hidden. Boot.ini has ....rdisk(1)partition(2)\....

Did you boot again from USB after the Text mode part of Setup?

This post has been edited by ilko_t: 07 November 2008 - 12:52 PM


#7 User is offline   warlock554 

  • Group: Members
  • Posts: 5
  • Joined: 03-November 08

Posted 08 November 2008 - 11:09 AM

Ok, so here's my bios configuration:
Posted ImagePosted Image

My partition configuration:
Posted Image

And my boot.ini file:
[Boot Loader]

Timeout=5

Default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS

[Operating Systems]

multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Second part of XP Professional setup from hd 1 part 1" /FASTDETECT

And yes, I've booted again to start the GUI mode.

This post has been edited by warlock554: 08 November 2008 - 11:17 AM


#8 User is offline   ilko_t 

  • MSFN Expert
  • Group: Super Moderator
  • Posts: 1,458
  • Joined: 06-December 06
  • OS:none specified
  • Country: Country Flag

Posted 08 November 2008 - 01:39 PM

Try deleting BOTH partitions on the hard disk while in Text mode and create 2 new ones.
Do NOT continue, but rather hit F3 and restart again in Text mode. Install XP in the first one of the newly created partitions.

In BIOS do you have a setting for hard disk mode AUTO, LARGE, LBA? Try changing it too.

This post has been edited by ilko_t: 08 November 2008 - 01:40 PM


#9 User is offline   wimb 

  • Senior Member
  • Group: Developers
  • Posts: 575
  • Joined: 21-March 07

Posted 09 November 2008 - 02:25 AM

I assume you are using a removable USB-stick which will be seen by BIOS as Harddisk (NOT as USB-HDD)
When you boot from USB-stick then normally USB-stick is HDD-0 and Local Harddisk is HDD-1

You have to Change for GUI Setup your BIOS Setting so that First Boot Device is HDD-0 (instead of USB-HDD)
which is in GUI mode your USB-stick, so that you boot via USB and
Windows folder will be found at HDD-1 by the setting of rdisk(1) in boot.ini on USB-stick
With your present BIOS Setting you are booting in GUI mode directly from HDD-1 which is
then your Local Harddisk. That does NOT work. You have to Boot via USB-stick which is HDD-0

This post has been edited by wimb: 09 November 2008 - 02:34 AM


#10 User is offline   warlock554 

  • Group: Members
  • Posts: 5
  • Joined: 03-November 08

Posted 09 November 2008 - 03:15 AM

Ok, I've changed the first boot device from USB-HDD to HDD-0. I redid the TXT part, booted again into USB, tried GUI mode... but without success. Is there anything I'm doing wrong? Please excuse my noobiness. :)

This post has been edited by warlock554: 09 November 2008 - 03:32 AM


#11 User is offline   wimb 

  • Senior Member
  • Group: Developers
  • Posts: 575
  • Joined: 21-March 07

Posted 09 November 2008 - 06:30 AM

You can try my NEW technique using USB_XP_Setup package

Install XP from USB AFTER Booting with PE from HDD or USB
http://www.boot-land...?showtopic=5306

In this way you are first booting in 30 seconds with LiveXP from RAMDISK,
which is loaded in few seconds with LiveXP BootSDI.img file on Harddisk Drive C:
or in about 5 minutes from bootable USB-stick made with Make_USB.cmd

For Install of XP you all the time Boot as normal from your Local Harddisk Drive C:
so that you don't have these BIOS problems.
So there is no booting from USB-stick involved when actually installing XP.

The XP Source Folder must be on USB-stick or on Partition 1 of ANY Harddisk.
If this is NOT the case, then the program will propose to
Copy the XP Source folder to the Install Target Drive, usually C: (being usually partition 1).

This post has been edited by wimb: 09 November 2008 - 07:15 AM


#12 User is offline   ilko_t 

  • MSFN Expert
  • Group: Super Moderator
  • Posts: 1,458
  • Joined: 06-December 06
  • OS:none specified
  • Country: Country Flag

Posted 09 November 2008 - 11:29 AM

View Postwarlock554, on Nov 9 2008, 02:15 AM, said:

Ok, I've changed the first boot device from USB-HDD to HDD-0. I redid the TXT part, booted again into USB, tried GUI mode... but without success. Is there anything I'm doing wrong? Please excuse my noobiness. :)

Did you try what I wrote you, post #8 ?

#13 User is offline   baazi 

  • Group: Members
  • Posts: 2
  • Joined: 10-November 08

Posted 10 November 2008 - 06:09 AM

i've got the same hal.dll problem when entering the gui mode after textmode. I did everything like it is described in the how-to, also carfully paid attention to set the right boot-order, to manually choose the usb-drive when booting every time. i also created only one partition (ntfs) and it's everything ok with the boot.ini...
the only thing i discovered is that the bios (phoenix trustedcore) of my brandnew samsung nc-10 automatically detects the usb-stick as an usb-hdd and there is no possibility to set the hhd0- and hdd1-thing. I'm only able to change the boot order (so hdd befor usb-hdd?!). Is this the problem in combination with the boot.ini, like wimb described above #9 ?
Is there any possibility to fix it?
thx tobey

#14 User is offline   wimb 

  • Senior Member
  • Group: Developers
  • Posts: 575
  • Joined: 21-March 07

Posted 10 November 2008 - 09:40 AM

When in GUI mode the Windows folder is NOT found on the default location,
it can be handy to use a boot.ini with Multiple Entries for the GUI Mode.
For USB_MultiBoot_10 it would be like this:

 [Boot Loader]
Timeout=20
Default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
[Operating Systems]
C:\btsec\XPSTP.bs="1. Begin TXT Mode Setup Windows XP, Never unplug USB-Drive Until Logon"
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Continue GUI Mode Setup XP + Start XP from HD 0 - Part 1" /FASTDETECT
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Continue GUI Mode Setup XP + Start XP from HD 0 - Part 2" /FASTDETECT
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Continue GUI Mode Setup XP + Start XP from HD 1 - Part 1" /FASTDETECT
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="Continue GUI Mode Setup XP + Start XP from HD 1 - Part 2" /FASTDETECT


where you can Manually Select the GUI mode Entry that is working for you.

Also it is important to remove before XP Setup from USB-stick
all other USB-drives like External Backup Harddisks and Cardreaders,
which could give unwanted shift in drive numbering.

This post has been edited by wimb: 10 November 2008 - 10:00 AM


#15 User is offline   baazi 

  • Group: Members
  • Posts: 2
  • Joined: 10-November 08

Posted 17 November 2008 - 03:44 AM

thx wimb, you're the best!
In fact it was the wrong rdisk-value due to usb-hdd! Installation worked fine.
thank you so much!

#16 User is offline   Big_W 

  • Group: Members
  • Posts: 1
  • Joined: 27-February 09

Posted 27 February 2009 - 05:17 PM

It still doesn't work for me. I got the same problem whole the time. I have already test to change the boot.ini with
[Boot Loader]
Timeout=20
Default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
[Operating Systems]
C:\btsec\XPSTP.bs="1. Begin TXT Mode Setup Windows XP, Never unplug USB-Drive Until Logon"
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Continue GUI Setup + Start XP from HD 0 - Part 1" /FASTDETECT
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Continue GUI Setup + Start XP from HD 1 - Part 1" /FASTDETECT
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="Continue GUI Setup + Start XP from HD 1 - Part 2" /FASTDETECT
multi(0)disk(0)rdisk(1)partition(3)\WINDOWS="Continue GUI Setup + Start XP from HD 1 - Part 3" /FASTDETECT
multi(0)disk(0)rdisk(2)partition(1)\WINDOWS="Continue GUI Setup + Start XP from HD 2 - Part 1" /FASTDETECT

pls can you explain more details because I don't get it what you really mean.
It got the hal.dll error whole the time. But if I press
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="Continue GUI Setup + Start XP from HD 1 - Part 2" /FASTDETECT
it says that windows could not start because of a computer disk hardware configuration problem......
plss helppp

#17 User is offline   wimb 

  • Senior Member
  • Group: Developers
  • Posts: 575
  • Joined: 21-March 07

Posted 28 February 2009 - 01:50 AM

View PostBig_W, on Feb 28 2009, 12:17 AM, said:

It got the hal.dll error whole the time. But if I press
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="Continue GUI Setup + Start XP from HD 1 - Part 2" /FASTDETECT
it says that windows could not start because of a computer disk hardware configuration problem......
plss helppp
So there is another problem as well.
How was your XP Source Folder prepared ?
Did you use nLite ? What version of XP do you use ?

Is your XP Source on USB-Harddisk and that you forgot to adjust Option 0) ?

Quote

For Install of XP on a modern system with SATA Drives it is needed to use DPsBase.exe
for Integrating in your XPSOURCE BTS DriverPack Massstorage with TXT Mode Enabled.
In that case a lot of Extra RAID SCSI and SATA Drivers (about 120 extra) are Integrated which appear in the
XP Setup BootFolder $WIN_NT$.~BT on USB-Drive and can prevent a lot of XP Install Boot Problems.
First use RyanVM Integrator and then use DPsBase to Improve your XP-Source.
Supports the use of BTS DriverPacks located in OEM Folder on USB-Drive
http://driverpacks.net/DriverPacks/


As alternative you can try:
Install XP from USB AFTER Booting with PE from HDD or USB
http://www.boot-land...?showtopic=5306
In this way you are insensitive to the hal.dll Error
Moreover, after booting with LiveXP into PE environment you are able to
use Disk Manager and can see what is the partitioning of your harddisk and
see which is the Active Partition e.g. the partition from which the computer will try to boot.
Also you can make then appropriate changes using Disk Manager or Acronis Disk Director available in LiveXP

This post has been edited by wimb: 28 February 2009 - 02:18 AM


#18 User is offline   dpressm 

  • Group: Members
  • Posts: 1
  • Joined: 22-March 09

Posted 22 March 2009 - 07:08 PM

OK I think I need some help with a non-standard problem.

My laptop will not work from the Built-in hard drive. So I have an empty bay (Thinkpad 42) So I have a hard drive in the Ultrabay (where the CD was) and am trying to make it bootable. I have created a bootable USB but when I get to the step where it does the install I have a problem that I believe is involved with the Boot.ini code:

C:\btsec\XPSTP.bs="1. Begin TXT Mode Setup Windows XP, Never unplug USB-Drive Until Logon"
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="2. and 3. Continue with GUI Mode Setup Windows XP + Start XP from HD 1" /FASTDETECT
multi(0)disk(0)rdisk(2)partition(1)\WINDOWS="Continue GUI Setup + Start XP from HD 2, use if installing on HD2" /FASTDETECT
c:\grldr="4. Start GRUB4DOS Menu - DOS FPY IMAGES + Linux + XP Rec Cons + Vista"


I need to bood from USB but then install onto the D drive - I think it would be:

multi(0)disk(1)rdisk(1)partition(1) ????

There is only one partition on the disk.

Thanks a lot.



BTW I am trying to resurrect this supposedly defunct machine for a friends son who can not afford a PC. It was in a corporate :"dead laptop" closet and I got it for free with no disk drives. I had a T43 with 2 drives and had hoped to just move the second hard drive to this machine.

As a test I have placed the C drive from the 43 which boots fine into the T42 second bay (with an empty first bay) and it tries to boot but it gets as far as "MUP.SYS" and then just dies so I figured that I must have some driver that does not work on the T42 - therefore I am trying to build a new boot drive using the T42 to make its own boot drive.

Does this make sense to you?

#19 User is offline   ilko_t 

  • MSFN Expert
  • Group: Super Moderator
  • Posts: 1,458
  • Joined: 06-December 06
  • OS:none specified
  • Country: Country Flag

Posted 23 March 2009 - 03:12 AM

Quote

when I get to the step where it does the install I have a problem
Would be helpful if you mention what actually the problem is ;)

Do you see the boot menu? 1. Begin TXT Mode Setup Windows XP, Never unplug USB-Drive Until Logon, 2. and 3. Continue with GUI Mode Setup Windows XP + Start XP from HD 1

What happens when you select 1? Does it start Text mode part of the setup? Does it complete Text mode?
Then what happens when you select "2 and 3"?

FYI- drive letters C, D etc. are given by windows and do not provide information about disks and partitioning. When describing similar problem use first hard disk/partition 2, second hard disk/partiton 1 etc. etc.

Quote

As a test I have placed the C drive from the 43 which boots fine into the T42 second bay (with an empty first bay) and it tries to boot but it gets as far as "MUP.SYS" and then just dies
Did you try Safe mode first?


You may also have a look at OffLineSysPrep which may help you transfer the existing Windows:
http://www.911cd.net...showtopic=19397

Have it redetect HAL (Auto configuration) and inject Standart MS mass storage drivers (advanced-->install standard IDE drivers), tick "Complete OffLineSysPrep without running SysPrep" as well. Then make the first reboot in Safe mode.

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2011 msfn.org
Privacy Policy