The previous version was downloaded 627 times.
The very first version had several bugs.
After their correction, I got feedback in 2-3 cases, that Windows XP could not be started any more (hal.dll missing, although that file still exists).
It was not clear, if that was caused by the installer (by wingrub) or not.

However, take that as a warning to backup your Windows XP before using this installer !

Install it. Then you have a new icon on your Desktop.
If you run it, you can install Puppy inside WindowsXP.
It will use the dutch mirror to download Puppy.
There are 3 "Help"-Buttons explaining how it works.

A special version of "Wingrub" is used, so that existing Linux-Grubs should not be disturbed.
You also can install a patched "image.gz".
You will need that, if Puppy starts, but bugs you with the message "usr_cram.fs not found".
This patch only works, if WindowsXP is installed to C:\ on the first partition on the first Harddrive with the NTFS-Filesystem (typical OEM-Setup).

The patch also includes a small change in the "resize2fs"-program: it is run without the "F"-Parameter. (see here: http://www.murga.org/%7Epuppy/viewtopic.php?t=3350 ).

MarkLast edited by MU on Tue 08 Nov 2005, 00:28; edited 1 time in total

Ok, I changed that.
It had a unix-lf, now I changed that to windows-lf.
But strange anyway, that just 0.5% of the people that downloaded it, reported a hal.dll -error.
One wrote, he uninstalled it later.
Maybe there he made an error somehow.
Thanks, Mark

First click on "install".
Now copy
c:\usr_cram.fs
c:\pup001
c:\puppylinux1.0.6\vmlinuz
c:\puppylinux1.0.6\image.gz
to the USB-Drive.

Then edit c:\Program files\Puppy-Linux-1.0.6 Installer for Windows XP\resource\puppyboot\menu.lst
to use the usb-drive instead of C:\
Finally click on "install wingrub".
But I don't know, if WinGrub supports USB-Drives.
If not, you need the wake-USB-Floppy from Peter Sieg (See http://www.murga.org/%7Epuppy/viewtopic.php?t=3352 )

Your program you made works great, but I must point out that:
" default=multi(0)disk(1)rdisk(0)partition(1)\WINDOWS " likes to take over first, making XP not even read " C:\boot\stage1="Puppy Linux1.0.6 ". So by adding " timeout=30 " to C:\BOOT.INI you can correct the problem.

A former first testversion was able to modify boot.ini more detailed, but lead to an error where lost my whole XP. So that is no longer available.

The current version is less dangerous, it simply adds the puppy-entry in the end, nothing more.

On my XP, the
timeout=30
entry is set by default, and it boots nice like that.

Important for anybody reading this:
Do not simply copy the content of the former message to your boot.ini.
if
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /fastdetect /NoExecute=OptIn
does not meet your systems configuration, you will not be able to start XP any more!

Be aware that modifications to boot.ini are highly critical!

OEM-Versions of XP don't even enable you to correct erratic entries with the rescue-CD.
You would have to build your own rescue-disk or CD to correct things.

----------------------------------------------------------------
"This situation occurs when setting up a dual boot situation with Windows 2000 and Windows XP (it may occur with other setups). After Windows XP's install routine has finished copying files, and is ready to boot to the GUI portion of SETUP, you may receive the 'Hal.dll missing' error. This has been traced to an incorrect BOOT.INI file

HAL is Microsoft's abbreviation for the Hardware Abstraction Layer, the technology and drivers that let the Windows NT, 2000, and XP operating systems communicate with your PC's hardware.

( really? it's just sooo much bull..t

HAL prevents applications from directly accessing your PC's system memory, CPU, or hardware devices (f ex video/sound cards). a method that can prevent many device conflicts and crashes. ufortunately, HAL sometimes also slows or stops DOS games and programs, which need to load their own memory managers or control hardware directly for better performance.

With HAL in the way, developers must rewrite or even abandon their older software in favor of newer, HAL-compatible versions. Microsoft has pressured hardware makers to provide or support technologies such as MMX, DirectX, and 3D technologies. XP also offers some new compatibility-mode features that let you run programs meant to run under earlier operating systems, but, frankly, most DOS-based and even some Windows-based games simply won't work with the new OS.

Tip: To see which HAL is currently installed, open Device Manager, and expand the Computer branch. The entry that appears in this branch corresponds to the currently installed HAL.

------------------------------

It's a common problem in dualbooting Linux/XP to.
Here's some suggestions when dual_booting goes amok

1. if you had W98 first, then installed linux and used it's (grub/lilo) multiboot option and now want to get back to only W98. use your W98 install_cd. Just install it as usual with whatever defaults you used last time you installed it. F ex the place you installed windows to, default is c:\windwows, if you changed that last time you installed to f ex c:\w98 , then just make your new installation to the same drectory. That will give you back your original installation with all your software in place.

Or make a boot floppy, then 'cd c:' then use 'cd windows' ( if that was your former placement/default ), then 'cd command' to got to your C:\windows\command.

Finish by writing ' fdisk /mbr ' while being in C:\windows\command.
Reboot, hopefully you will now have your W98 back.

You will lose access to your linux though it will still exist on your linuxpartition.
--------------------------------------------------

2. if you had xp first and then installed linux with its (grub/lilo) bootmanager. Then you shold be able to see/boot into XP whereafter it hangs. And the problem is this hal.dll...
Press 'f8' directly after chosing to boot into your XP to test.

Chose 'safe mode'. If it's hal.dll you could try the options furth down with Cd and Recovery Console. Just remember that the problem isn't really hal.dll but the incorrect BOOT.INI file, so it wont help to just put in a new hal.dll.

You should first try to make a correct BOOT.INI file, if that doesn't help you continue with installing a new hal.dll.

(XP_1)

----------------------------------------------------

1. Configure the computer to start from the CD-ROM or DVD-ROM drive. For information about how to do this, see your computer documentation, or contact your computer manufacturer.
2. Insert the Windows XP CD-ROM into your CD-ROM or DVD-ROM drive, and then restart your computer.
3. When you receive the "Press any key to boot from CD" message, press a key to start your computer from the Windows XP CD-ROM.
4. When you receive the "Welcome to Setup" message, press R to start the Recovery Console.
5. If you have a dual-boot or multiple-boot computer, select the installation that you have to use from the Recovery Console.
6. When you are prompted, type the administrator password, and then press ENTER.
7. At the command prompt, type bootcfg /list, and then press ENTER. The entries in your current Boot.ini file appear on the screen.
8. At the command prompt, type bootcfg /rebuild, and then press ENTER.

This command scans the hard disks of the computer for Windows XP, Microsoft Windows 2000, or Microsoft Windows NT installations, and then displays the results. Follow the instructions that appear on the screen to add the Windows installations to the Boot.ini file. For example, follow these steps to add a Windows XP installation to the Boot.ini file:

a. When you receive a message that is similar to the following message, press Y: Total Identified Windows Installs: 1
[1] C:\Windows
Add installation to boot list? (Yes/No/All)

b. You receive a message that is similar to the following message: Enter Load Identifier
This is the name of the operating system. When you receive this message, type the name of your operating system, and then press ENTER. This is either Microsoft Windows XP Professional or Microsoft Windows XP Home Edition.

c. You receive a message that is similar to the following: Enter OS Load options When you receive this message, type /fastdetect, and then press ENTER. Note: The instructions that appear on your screen may be different, depending on the configuration of your computer.

9. Type exit, and then press ENTER to quit Recovery Console. Your computer restarts, and the updated boot list appears when you receive the "Please select the operating system to start" message.

-----------------------------
Of_course this may expect you to have used XP:s bootmanager to install linux - witch wich you didn't, right, but it should give you your XP back.

You will lose access to your linux though. Most probably, it will find your linuxpartition to and offer to partition it into NTFS to, or Fat32 if thats more to your liking. At least i believe you should have this option somwhere,you have to ...read carefully... before acting.

----------------------------------------------

And...(XP_2)
-----------------------------------------

IF HAL.DLL still is 'Missing' you could try this.

Boot from your CD and follow the directions below to start Recovery Console. Insert the Setup compact disc (CD) and restart the computer. If prompted, select any options required to boot from the CD.
When the text-based part of Setup begins, follow the prompts;
choose the repair or recover option by pressing R.

If you have a dual-boot or multiple-boot system, choose the installation that you need to access from the Recovery Console.
When prompted, type the Administrator password. (if you didn't create one try pressing enter).

At the system prompt, type Recovery Console commands; type help for a list of commands, or help commandname for help on a specific command.
Most likely you will need to expand the file from the CD. The command would be expand d:\i386\hal.dl_ c:\windows\system32\hal.dll.

Substitute d: for the drive letter of your CD. Once you have expanded the file type "exit" to exit the Recovery Console and restart the computer.

sorry, to long a post that one, it's just that i to have had those problems.
And those are the answers i've found. Not very good, but then again, it's Xp.
As the drivers for this laptop (PaceBlade) only works with XP i need to keep it for now.

What i really would prefere is a small 'bootfixer' that you could start from a system_floppy with options to restore your mbr to its original condition,
f ex it could make an image of the mbr directly after installing Linux.
One version before lilo/grub,one after. That would be nice to have.

How much for that Puppy in the window
Is it possible to download and install it directly on my ext3 from my XP?

Or downloading a ISO on my vfat, then install on my ext3/swap via a system_floppy?
As i have no CDburner, that is...

Or is there a better/other sollution ?_________________No Mind
Never matter

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum