guests Posted November 24, 2021 Share Posted November 24, 2021 (edited) 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 Edited November 24, 2021 by guests Link to comment Share on other sites More sharing options...
Tripredacus Posted November 24, 2021 Share Posted November 24, 2021 Typically when seeing the individual files being loaded, the ones last shown on the list before a crash or freeze are the ones that loaded properly, and it is the following ones that are causing the problem. You should do the step-by-step confirmation boot to hopefully find out which item is actually causing the problem. Also your hardware may not be correct for Windows 2000, can you post your specs? Link to comment Share on other sites More sharing options...
guests Posted November 24, 2021 Author Share Posted November 24, 2021 (edited) 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 Edited July 15, 2022 by guests Link to comment Share on other sites More sharing options...
pcalvert Posted December 30, 2021 Share Posted December 30, 2021 I suspect that what happened is that Windows 7 somehow tampered with the partition that Windows 2000 is on. 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. Link to comment Share on other sites More sharing options...
guests Posted January 5, 2022 Author Share Posted January 5, 2022 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 Link to comment Share on other sites More sharing options...
guests Posted January 5, 2022 Author Share Posted January 5, 2022 (edited) 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 Edited January 13, 2022 by guests 1 Link to comment Share on other sites More sharing options...
jaclaz Posted January 5, 2022 Share Posted January 5, 2022 3 hours ago, guests said: guess what, found the culprit after headaches 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 problem is caused by even just starting CCleaner Yes and no. Meaning that surely the (crappy and mostly unneeded and generally speaking misused) CCleaner is the "trigger", but the base issue is almost surely at a lower level. As pcalvert wrote, the Windows 2000 NTFS filesystem is (not much, but IMHO "enough") different from the Windows 7 one that some types of disk access may well create havoc. Besides, even "mixing" XP with Vista in some (not-so-unusual) cases can make all logical volumes inaccessible, only for the record/FYI: A good idea (my personal advice) is to (for a production machine): 1) DO NOT allow the two OS instances to "see" each other, or if you prefer, the two OS's MUST be installed to separate partitions and the Windows 2000 partition should not be able to see the Windows 7 one, and viceversa (you can use a bootmanager like grub4dos to selectively hide at boot time the "other partition") 2) DO NOT use Disk Manager from the Windows 2000 on the disk (provided that the disk has been originally partitioned/formatted under 7) 3) DO NOT use (if possible on your setup) logical volumes (because the XP/Vista Disk Manager bug is "nasty" and it is very likely that the same exist in 2000/7) 4) If you need to exchange data between the 2000 and the 7 use a third FAT32 partition (you will be limited to 4 GB files, though) jaclaz 1 Link to comment Share on other sites More sharing options...
guests Posted January 10, 2022 Author Share Posted January 10, 2022 (edited) @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 Edited July 13, 2022 by guests 1 Link to comment Share on other sites More sharing options...
guests Posted July 15, 2022 Author Share Posted July 15, 2022 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 1 Link to comment Share on other sites More sharing options...
jaclaz Posted July 16, 2022 Share Posted July 16, 2022 14 hours ago, guests said: 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 Which is "another" way to do what I suggested earlier (hiding the "other" partition through a bootmanager). If a partition is marked as "hidden" it is "more protected" than having the drive letter removed. Probably you missed in my earlier post how the hiding (of the "other" partition, and the unhiding of the currently chosen one) in a bootmanager works, it is done on-the-fly at boot time, before the old (or new) OS is booted. The "other" partition is never auto-mounted by the "current" OS (as opposed to be automounted but without a drive letter). Typical grub4dos menu.lst example: title Windows 2000 hide (hd0,1) unhide (hd0,0) makeactive (hd0,0) root (hd0,0) chainloader +1 (or chainloader /ntldr) title Windows 7 hide (hd0,0) unhide (hd0,1) makeactive (hd0,1) root (hd0,1) chainloader +1 (or chainloader /bootmgr) (the makeactive directive might be not strictly needed, but by including it when the ntldr or the bootmgr loads the disk will appear as a "standard" disk with the "current" partition active) jaclaz Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now