Ok for windows 2k observations: when the startup bar appears there is no text that sais"press F8 for advanced options" The windows 2k appears and then the barr fills half way and tehn stops then blue screen: " ***STOP: 0x00000050 (0xE17FF000, 0x00000000, 0xF0930855,0x00000001)PAGE_FAULT_IN_NONPAGE_AREA If this is the first time you've seen this stop error screen, restart yuor computer. if this screen appears again fallow these steps: Check to make sure that any hardware or software is properly installed.If this is a new instalation ask your hardware or software manufacuturer for any windows 2000 updates you might need. If problem continues, disble or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadoing. If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select Advaced StartUp Options, and then select Safe Mode. Refer to your getting started manual for more information on troubleshooting errors. " end of error message. I hope this helped...

0

But could you run both the W2k and Win98 systems back then? Looks like "\WINDOWS\SYSTEM32\CONFIG\SYSTEMd " is incomplete. Was the file name it was looking for just system? Could you go into disk manager (in Manage Computer)and tell me what it says for each of the partitions? ie partition type, what its formated as, size, whether its active or not. In the mean time I'll check out your 50 stop code. Keep it up, michael

0

Your 50 Stop is a catch all for any type of memory erroring (main RAM, video, L2 cache). The error is happening on a READ. Depending on the age of your Toshiba, it could be a problem with Advanced Power Management, LAPTOP.sys (Q234744), the type of video card and its driver, or reference these Microsoft Knowledge Base articles Q279491/296872 and Q265509 on the Microsoft support web site. One suggestion I'd like you to try is: 1. Add the /sos switch after /fastdetect (with a space between them) to both lines of your boot.ini file. 2. Format 2 floppies in W2k. 3. Copy the XP versions of NTDETECT.COM and NTLDR as well as your boot.ini to one floppy. 4. Copy the W2k versions NTDETECT.COM and NTLDR as well as your boot.ini to the other floppy. 5. Boot each floppy and see what happens when you try to boot XP and W2k. Your W2k NT files should have date stamp 5/4/01 or 5/20/01. The XP ones 8/18/01.

0

Ok under Win2k in Disk Management: Windows2000 (C:) 9.79GB NTFS HEALTHY (boot) Windows XP professional (E:) 8.84 GB NTFS HEALTHY(SYSTEM) where (D:) in Win2K is the DVD But under DOS WIN2K is on (D:) And Win XP is on (C:) Type "basic" for both, layout "partitioned" ... Before and now, I am able to boot both operating sistems if i replace the NTLDR as mentioned in the first message.I will try the flopy thing, but from what i know it will work but it will not be practical.

0

That's the information we needed! What I was also looking for was the location of each partition (lower right box beside DISK0)and whether the 2nd partion was a primary partition or an extended partition with a logical disk. Now I understand your problem though. There is a limit to how far in the disk a "boot" partition can be (the OS that you want to run) and how big the "system" partition can be (contains the bootloader code). Its about 7.8GB. Reference Q114841, Q224526, Q314057 and The MOLE #13, all on microsoft.com Like I had said before, it matters how the systems are loaded. Most OEM systems are not loaded, they're duped or imaged or ghosted, take your pick of terminology. You can resize the partitions with something like Partition Magic (latest version will handle NTFS 5, I think). You should know that you can copy one partitions contents using the other partitions OS. But cannot format or re-partition the "system" partition (its always in use, unless you CD or floppy boot). You could remove the HD from the laptop, and hook it up to an IDE channel (there is an adapter availible for this) on another machine running at least W2k and with lots of free disk space. Then you could just copy (or ghost) each patition over to the other machine's HD, repartition your drive and copy back (or ghost back). Or, copy the contents of the 2nd partition over a network to some storage space. Then using the XP CD to boot, delete all the partitions, repartition to something like 4GB, 4GB and the rest (10 GB). Install XP, network back to the storage space and copy the second partition back. You'll need your current boot.ini file to boot the 2nd partition. And upon thinking on that one some more, this might just work, depending on how much data is on each partition. With the 1st primary partition being XP, you might be able to boot the XP CD, delete the 1st partition, re-partition it to something like 6GB, install XP and then copy the contents of the 2nd partion into a folder on the 1st partition. Using XP, delete and repartition the rest of the HD into a 12GB partiton. Then, FIRST, copy the \winnt directory from the folder on the 1st partition to the second partition. This should insure that the NTOSKRNL.exe and HAL.dll are within that 7.8GB limit. Lastly, copy the rest of the folder on the 1st partition to the second partition. DON'T USE MOVE or CUT just COPY, just to be safe. Other than those ideas, you could of course repartition and reload everything and start fresh. Let me know! michael

0

Ok some other observations: i ran the floppy's and as predicted with the win2K floppy i can start only win2K and vice versa. If i try to run Xp with the Win2K floppy i get teh same error as described above. On another note when i started win2K with the Disk For win2K i noticed that it checks the (E:) first and then it goes to its boot partition which is (C:) so thinking back when i try to boot with the XP floppy i can't be 100% shure but this is the place where it crashes. when it chcks the other partition and it finds the XP NTLDR instead of its own. The NTLDR for XP probably (does it?) contain the XP driver assignments which differ from the Win2K ones?!. As for the system, it is half a year old, Satelite 1800, 128 RAM, P3 885Mhz, 6-8 Mb video RAM not sure cuz when i purchased it it said 8 but there are 6 missing from the motherboard RAM so I'm guessing 6Mb. Soundcard, crappy but didn't have any problems with it. 8x DVD/ROM - (E:) - Under XP (D:) - Under 2000 if by date stamp you mean last modified : Win2K NTLDR 05/08/01 WinXP NTLDR 08/23/01 i was thinking of looking for someone with Win2K and XP and get their NTLDR. So , any ideas ... anyone

0

ok - there are several problems adn questions. I don't doubt what you said, and i've read that too, i just didn't know it was 7.8 GB. But i can't help wonder why XP still works, if that is true. Secondly this laptop is identical to another 150 in my school. I know people have managed to make it work without tampering with the partitions. Why do i say this is that in order to access the network at school all the laptops have to be configured and the admin does not bother with fixing the operating sistem, he just dumps the imagine onto the harddrive and starts over fresh. Thus if Win2000 becomes unoperable, or unreparable i can not reinstall it because it will eventualy end up with him and he will reformat and dump the imagine. As for the people that have done it before they either have had no problems like i do or have left the country. In short i am scrued 1. I can not tamper with the Win2K partition otherwse i would of done it already. 2. I have a desktop but it has a smaller hard drive then the laptop ths i can not transferr all the info over. So if there isn't any other solution could i format the drive with XP and then reinstal 98, and then update to Xp? I know 98 works on that partition. Any other sugestions? Again thank you in advance...

0

Q224526 - reading the file i found a passage that sais :"Other operating systems, such as Microsoft Windows 95 OEM Service Release 2, Microsoft Windows 98, and Microsoft Windows 2000, can boot from larger partitions because these operating systems were written after the computer industry defined a new standard for BIOS INT13 functions (the "INT13 extensions") and implemented this new functionality on manufactured motherboards"

0

Reading on i found a page that talks about WinXP and how NTLDR will generate a line in BOOT.INI, a signiture if - NTBootdd.SYS has been used to find the boot sector because INT13 has not been anle o find it. http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/winxppro/reskit/prmc_str_masc.asp thus after reading these files one would draw the conclusion that this set up should work....

0

In response to 12, NTLDR doesn't contain driver assignments per se, but does contain minifile system drivers to find and load the OS from different file system formats (FAT, FAT32, NTFS). In response to 13, XP worked because the OS is within the 7.8GB boundary. My last suggestion of using XP to resize the 1st partition has nothing to do with tampering with W2k. Another OS that can read NTFS can copy anything but encrypted files, properly, on the HD its on. Putting Win98 back down on FAT32 may work as it handles the disk differently from NTFS. Regarding #15, thanks for the info! SCSI drives are different and require the SCSI controller driver being renamed to NTBOOTDD.sys. The article (and some more I read) does seem to indicate that by using the signature of the partition and changing the ATA controller driver name to NTBOOTDD.sys (and putting it in the root directory of C:), you can over come the 7.8 GB barrier. It does mention that the INT13 has to be disabled in the BIOS, you should be able to check. You could try the bootcfg command in Command Console. Do check with someone else and see what they have in their boot.ini file (if they have the signature option) and their partition sizes. And by all means, try their loaders, specifically if they have a NTBOOTDD.sys file. Remeber you'll need to change the signature number in your boot.ini file. And while you probably don't want to, you could always get your admin to re-image the drive.

0

Michael - well i'll keep on trying sadly i have other work, thank you for all the help, if you find any other solutions pleasse let me know. I'll meet the admin soon so I'll chat with him but i doubt i would get to far. If i do fix it i'll post it. I'll try the above and see where they get me. If i recall the BIOS settings there isn't a mention of INT13 but i'll give it another look, TOSHIBA is not that flexible some times. You mentione that i would have to change the signiture file...how do i do that? The file that i read mentioned that the computer will record in one of the signiature fields the cluster field from where the partition starts or ends... or someting like that, how will i know how to set it? And as i mentioned before, at this time i don't have anyone with the same sistem and same operating sistems. Once again thank you for all the help and i'll get back if i have something new.

0

Bios does not have anything mentioning INT13 but in bootcfg i found the comand "disableredirect" should i use this? because everything elce looks fine. It detects both systems with the right partitions.

0

Sorry, I don't know ins and outs of that particular Toshiba model. I could not find any mention of the "disableredirect" in Rojacks Pot BIOS guide. Unless that option was in the IDE or disk section of the BIOS, I doubt whether it would help. Regarding the disk signature: NT, W2k and XP put a "signature" (ie a number) for each of the partitions, somewhere in the MBR (varies with the OS and disk format). You wouldn't be changing it, but you would need to know what it is to add to the signature option in the boot.ini file. You can use the Resource kit app Diskprobe.exe to find out what it is (be careful with this program, it can write your disk). Q149927 discusses it, as does CH32 in the W2k Res kit. Unless you have verified that another of the "identical to another 150 in your school" (response 13) laptops is using the signature option in the boot.ini file, this point is moot. I am pretty sure that you used to be able to dual boot Win98 and W2k because of the FAT32 formating of the first partition. That might work for XP as well. As I said before, FAT32 drives are handled differently than NTFS drives during the boot process. You never did say whether or not the two partitions were both primary, or primary and extended.

0

Tryed with the Fat 32 still the same error messages as before. There is no difference so far between fat32 and NTFS as the NTLDR is concerned. AS for the other laptops that might have something like this i don't have any at this point.

0

Radu, And here I thought this thread was abandoned. I still think you're running into the 7.8GB boot boundary, but I have no way of trying your setup out as my biggest drives are only 10GB. You said that you tried the FAT32 primary partition way. How did you do it? And maybe I assumed to much regarding your boot.ini file, you never did post it. The only thing I can suggest at this point is to re-post your problem, referencing this post (#15998), so that someone else can take a crack at this. Cheers michael I actually came back to this thread to just to post the way to get the Signature of a disk (so that I could reference it online). In a command window, start diskpart diskpart select disk 0 (or 1 or 2) detail disk the signature shows up as DISK ID. It is only available (in this program) for the 1st primary partition (tried with a 2nd primary partition, no signature listed), so this won't help in this situtation. REMEMBER that partitions start being numbered from 1, not 0. I still think this is for SCSI booting, but not having SCSI drives, I cannot test this.

0