guests

also another important is from the new operating system to disable the drive letter of the second partition disk that has the old operating system so it will not show to the computer folder and will only show the drive letter of the first partition disk that has the new and that solves the problem completely

@jaclaz thanks for the advice steps and reply "....the two OS's MUST be installed to separate partitions...." they were already installed to different partitions "....(you can use a bootmanager like grub4dos to selectively hide at boot time the "other partition")" but if you hide the other operating system you will not be able to select and use it "....(provided that the disk has been originally partitioned, formatted under 7)" before an installation every operating system should format its own partition cheers

guess what, seem to have found the culprit after reinstalling all the drivers and applications from the start and testing them individually, the only application that was left to test was one that removes junk from the machine such as the CCleaner from Piriform and.... voila! the crash is caused by even just starting CCleaner but there seem to be and other applications that cause such crashes

sorry for the delay, collecting information and.... sending @pcalvert thanks for the interest "I suspect that what happened is that Windows 7 somehow tampered with the partition that Windows 2000 is on." the windows 2000 somehow tampered otherwise it wouldn't crash at the start up by the way it shouldn't conflict with the other partition of the disk "Do not use Windows 7 to write to the Windows 2000 partition and vice versa. And make sure that Windows 7 is not configured to automatically check or defragment the Windows 2000 partition (and vice versa). The reason why this is likely to matter is that Windows 2000 uses an older version of the NTFS file system." don't think it's that one that matters so much because reinstalled both windows 7 and windows 2000 and copied some files from the old to the new and from the new to the old and didn't had problems

sorry for the delay, collecting information and.... sending @Tripredacus thanks for the interest, really appreciating it (because at majorgeeks.com they mocked the situation and at microsoft.com they didn't bother to reply at all) "You should do the step-by-step confirmation boot to hopefully find out which item is actually causing the problem." you mean with the console that is shown with the F8 key? "Also your hardware may not be correct for Windows 2000, can you post your specs?" the machine is an old by now MSI K9NBPM2-FID main board with AMD Athlon 64 3200 2.01 GHz processor and 2 GB RAM, don't think it's the one that is so much incorrect because in the past we had installed windows XP professional with windows 2000 professional and didn't had problems, the problems are occurring recently also we had experimented by copying those four system32 files from the i386\driver.cab\ and the i386\SP4.cab\ of the windows 2000 original CD but after it loads the start up screen it crashes showing a blue screen so copied back again the back up files and left them as they were

Greetings We have windows 7 professional operating system and have installed and the old windows 2000 professional operating system because some applications have other results in new windows and other results in old windows, both windows were installed successfully and work fine but after a while when trying to open windows 2000 it crashes at the start up, in safe mode it shows that the files that crash are the HAL.DLL, KERNEL32.DLL, NTDLL.DLL, NTOSKRNL.EXE Any solution to this problem? Thank you