Just a thought, not really relating to wine. On my system, the NT boot loader is in the boot sector of the first fat partition (primary), and is loading via lilo's chain loader without problem. All the systems I know of have the NT bootloader in the partition, I think the code in the MBR just directs to the NT loader in a partition. Have you tried booting from the NT CD and using the repair options (do you have a current ERD, if not it might be able to fix it anyway). I'd suggest making a linux boot floppy first though. Jeremy "Jim Morash" <jmorash@mit.edu> wrote in message news:d39f5530.0111081628.719f422f@posting.google.com...> I have probably a rather unusual problem. I have a computer with WinNT > already installed on it, plus RedHat7.2, and would like to try and > create a repair disk for the WinNT install (I'm no longer able to boot > NT, though I have no problem starting the NT bootloader - after I > choose Windows NT 4.0 and it starts to boot, I get a BSOD with > reference to being unable to access the bootloader (which was just > running...!?). So, I thought I might try and run rdisk.exe and create > a repair disk, using Wine. The only problem is, I can't get rdisk.exe > to access the floppy drive. Any suggestions? > > From my ~/.wine/config: > > [Drive A] > "Path" = "/mnt/floppy" > "Type" = "floppy" > "Label" = "Floppy" > "Serial" = "87654321" > "Device" = "/dev/fd0" > > I'm not sure whether /mnt/floppy should be mounted or not when trying > to do this. I tried it both ways and got the same error message from > rdisk.exe: > > "Repair Disk Utlity is unable to get configuration information for the > floppy drive" > > and this spew of stuff in the controlling xterm: > > fixme:ntdll:RtlDosPathNameToNtPathName_U > (L"A:\\",0x406160ac,00000000,00000000) > fixme:ntdll:NtOpenFile > (0x406160f0,0x00100003,0x406151cc,0x406151e4,0x00000003,0x00000010) > stub > fixme:ntdll:NtQueryInformationFile > (0x00000000,0x406151e4,0x406151ec,0x00000004,0x00000011),stub! > fixme:ntdll:NtFsControlFile >(0x00000000,0x00000000,(nil),(nil),0x406151e4,0x00090083,(nil),0x00000000,(n il),0x00000000):> stub > fixme:ntdll:NtDeviceIoControlFile >(0x00000000,0x00000000,(nil),(nil),0x4061607c,0x00070000,(nil),0x00000000,0x 4061604c,0x00000018):> empty stub > fixme:ntdll:NtDeviceIoControlFile >(0x00000000,0x00000000,(nil),(nil),0x4061607c,0x00070c00,(nil),0x00000000,0x 40615e4c,0x000001e0):> empty stub > > > I'm using Google Groups to post this and am pretty rusty on usenet, so > if you could email me a copy of your response that would make my life > easier! Thanks very much for your time, whoever reads this. > --Jim Morash > jmorash@mit.edu
I have probably a rather unusual problem. I have a computer with WinNT already installed on it, plus RedHat7.2, and would like to try and create a repair disk for the WinNT install (I'm no longer able to boot NT, though I have no problem starting the NT bootloader - after I choose Windows NT 4.0 and it starts to boot, I get a BSOD with reference to being unable to access the bootloader (which was just running...!?). So, I thought I might try and run rdisk.exe and create a repair disk, using Wine. The only problem is, I can't get rdisk.exe to access the floppy drive. Any suggestions?
On 8 Nov 2001, Jim Morash wrote:> I have probably a rather unusual problem. I have a computer with WinNT > already installed on it, plus RedHat7.2, and would like to try and > create a repair disk for the WinNT install (I'm no longer able to boot > NT, though I have no problem starting the NT bootloader - after I > choose Windows NT 4.0 and it starts to boot, I get a BSOD with > reference to being unable to access the bootloader (which was just > running...!?). So, I thought I might try and run rdisk.exe and create > a repair disk, using Wine. The only problem is, I can't get rdisk.exe > to access the floppy drive. Any suggestions?...> if you could email me a copy of your response that would make my life > easier! Thanks very much for your time, whoever reads this. > --Jim Morash > jmorash@mit.eduI don't know it it will help, but do you use a --winver? If you don't, Wine will tell the app it is win95. This may encourage the app to misbehave. I'd try --winver nt40, --winver nt351, and maybe even --winver win31. Maybe exporting the NT registry and feeding it to <wine>/programs/regapi would help too. I don't know if regedit.exe or whatever works in wine, though. You don't say how you came by the broken NT bootloader. Did you install lilo into the MBR? I think there is a hidden NT install option to make it install its bootloader into the partition boot sector where lilo (or grub) can chain boot it, but by default part of the NT loader goes in the MBR. I don't know this first hand, I used wfw 3.11 for a while until I got juno working with Wine-970914 then gradually wfw 3.11 atrophied from 2 little vfat partitions to a tar.gz. Lawson Q: How many IBM CPU's does it take to execute a job? A: Four; three to hold it down, and one to rip its head off.
Jim Morash <jmorash@mit.edu> wrote:> I have probably a rather unusual problem. I have a computer with WinNT > already installed on it, plus RedHat7.2, and would like to try and > create a repair disk for the WinNT install (I'm no longer able to boot > NT, though I have no problem starting the NT bootloader - after I > choose Windows NT 4.0 and it starts to boot, I get a BSOD with > reference to being unable to access the bootloader (which was just > running...!?). So, I thought I might try and run rdisk.exe and create > a repair disk, using Wine. The only problem is, I can't get rdisk.exe > to access the floppy drive. Any suggestions?Yep. Get someone to mail a disk image and dd it to your floppy.> and this spew of stuff in the controlling xterm:> fixme:ntdll:RtlDosPathNameToNtPathName_U > (L"A:\\",0x406160ac,00000000,00000000) > fixme:ntdll:NtOpenFile > (0x406160f0,0x00100003,0x406151cc,0x406151e4,0x00000003,0x00000010) > stub > fixme:ntdll:NtQueryInformationFile > (0x00000000,0x406151e4,0x406151ec,0x00000004,0x00000011),stub! > fixme:ntdll:NtFsControlFile > (0x00000000,0x00000000,(nil),(nil),0x406151e4,0x00090083,(nil),0x00000000,(nil),0x00000000): > stub > fixme:ntdll:NtDeviceIoControlFile > (0x00000000,0x00000000,(nil),(nil),0x4061607c,0x00070000,(nil),0x00000000,0x4061604c,0x00000018): > empty stub > fixme:ntdll:NtDeviceIoControlFile > (0x00000000,0x00000000,(nil),(nil),0x4061607c,0x00070c00,(nil),0x00000000,0x40615e4c,0x000001e0): > empty stubUgh. Not good. Implement it if you want to stand *any* chance of getting it to work. -- Andreas Mohr, Renningen, Germany In case you need to contact me after expiry of temporary email address: my eternal (hopefully) email address is frqr2001 at the domain sneakemail.com
On Fri, 9 Nov 2001 whit@giftie.alien.org wrote:> /sbin/lilo -uOh, there is another possibility. Maybe /etc/lilo.conf contains a typo left by the last System Administrator, and lilo is trying to chain-boot a swap partition it was told is NT. Maybe there was never anything wrong that could not be fixed by reinstalling lilo with an accurate lilo.conf. Lawson panic: detected rogue system administrator!! ---cut here ________________________________________________________________ GET INTERNET ACCESS FROM JUNO! Juno offers FREE or PREMIUM Internet access for less! Join Juno today! For your FREE software, visit: http://dl.www.juno.com/get/web/.