The hal.dll error is often caused by a badly configured boot.ini file. Here's my guess about what happened:
1. The SuSe installer rewrote your partition table. It changed the number of your windows partition; for instance if it was hda1 before it could now be on hda3. (Why it would do this, I don't know, but it could. I know the Windows installer sometimes does.)
2. Your boot.ini file now points to a partition that is no longer valid. The partition's bootcode functions normally, but as soon as it looks for the operating system, it can't find anything. hal.dll just happens to be the first thing it can't find, so that's what it shows an error for.
If this is the case, here's what I would do:
1. If your windows installation is on a FAT32 partition, you should be able to edit boot.ini from SuSe. Make sure it points to the right partition, and fix it if it doesn't.
2. If your partition can't be edited from SuSe (for instance, if it's NTFS), you may have to make a bootable disk in order to modify boot.ini. Again, make sure boot.ini points to the right partition, and fix it if it doesn't.
here's microsoft's page on editing boot.ini
Hope this helps!