NT 4.0 cannot see my W2K partition - any hints?

[Stefan Bischof]

My NT 4.0 (SP6a) is on a primary partition (drive c:), my Win2K (SP4)
on a logical drive in an extended partition. W2K can see the NT 4.0
drive , but not vice versa. Are there any drivers that I can copy to
make NT see the W2K drive?

Have looked in various archives for this poblem , but could't find it.
If this question has been covered, please point me to a URL.

TIA,
-Stefan

[Ghostrider]

Stefan Bischof wrote:
My NT 4.0 (SP6a) is on a primary partition (drive c:), my Win2K (SP4) on a logical drive in an extended partition. W2K can see the NT 4.0 drive , but not vice versa. Are there any drivers that I can copy to make NT see the W2K drive? Have looked in various archives for this poblem , but could't find it. If this question has been covered, please point me to a URL. TIA, -Stefan

How was the Win2K partition formatted - FAT32? Take a look at
www.sysinternals.com for programs that might allow Windows NT
to look into a FAT32 partition.

[Chris]

On Fri, 03 Oct 2003 17:55:08 -0700, Ghostrider <-00-@fitron.142>
wrote:
Stefan Bischof wrote: My NT 4.0 (SP6a) is on a primary partition (drive c:), my Win2K (SP4) on a logical drive in an extended partition. W2K can see the NT 4.0 drive , but not vice versa. Are there any drivers that I can copy to make NT see the W2K drive? Have looked in various archives for this poblem , but could't find it. If this question has been covered, please point me to a URL. TIA, -StefanHow was the Win2K partition formatted - FAT32? Take a look atwww.sysinternals.com for programs that might allow Windows NTto look into a FAT32 partition.


Also, the NT4 install must be at least SP4 (or was it SP3) which
updates the NTFS support to the version used in W2K/XP.

-Chris

[Stefan Bischof]

On Fri, 03 Oct 2003 17:55:08 -0700, Ghostrider wrote:
How was the Win2K partition formatted - FAT32? Take a look atwww.sysinternals.com for programs that might allow Windows NTto look into a FAT32 partition.

No, the W2K system is NTFS. So NT 4 is supposed to see it. :-/
Thanks.
-S.

--
Share what you know, learn what you don't.

** Please make the obvious changes to my address when replying by email.
** Bitte nehmen Sie die offensichtlichen Veränderungen an meiner Adresse vor, wenn Sie per Email antworten.

[Stefan Bischof]

On Sat, 04 Oct 2003 06:47:11 GMT, chris@nospam.com wrote:
Also, the NT4 install must be at least SP4 (or was it SP3) whichupdates the NTFS support to the version used in W2K/XP.-Chris

As I already wrote, NT has got SP6a. And the W2K systenm is NTFS.
Thank you for your reply.
-S.

--
Share what you know, learn what you don't.

** Please make the obvious changes to my address when replying by email.
** Bitte nehmen Sie die offensichtlichen Veränderungen an meiner Adresse vor, wenn Sie per Email antworten.

[Chris]

On Sat, 04 Oct 2003 13:57:06 +0200 (CEST), "Stefan Bischof"
<nospamplease.stefan.bischof@netic.de> wrote:
On Sat, 04 Oct 2003 06:47:11 GMT, chris@nospam.com wrote:Also, the NT4 install must be at least SP4 (or was it SP3) whichupdates the NTFS support to the version used in W2K/XP.-ChrisAs I already wrote, NT has got SP6a. And the W2K systenm is NTFS.Thank you for your reply.-S.

Sorry, I missed that fact that SP6a was already installed.

I have run into this before when the NT4 system was installed onto a
FAT partition. Then another NT4 nstall was installed, creating a new
NTFS partition using the installer.

The problem was that the original NT4 system did not have the NTFS
driver running. Try looking under the devices control panel and see
if there is a ntfs driver that is disabled or set to manual. I would
set it to system rather than boot because if the driver fails to load
correctl, you'll blue screen on boot. I don't have a NT4 system handy
to tell you the exact device driver name, but I think the actual file
is ntfs.sys.

Incidentally, what does windisk think of the partition? I think even
if the ntfs driver isn't loaded, it should properly identify it based
on the partition table. If it doesn't see the whole disk, I would
ensure you have the MS IDE drivers loaded. I've had problems with the
PIXIDE drivers not seeing the whole drive and causing missing
partitions.

-Chris

[Stefan Bischof]

On Sat, 04 Oct 2003 16:45:51 GMT, chris@nospam.com wrote:
The problem was that the original NT4 system did not have the NTFSdriver running. Try looking under the devices control panel and seeif there is a ntfs driver that is disabled or set to manual.

W2K brought a new ntfs.sys to the NT 4.0 system because the W2K installation
changes all present NTFS partitions which it can see to NTFS 5. Two years ago
this had the consequence that due to the old ntfs.sys Windows NT 4.0 couldn't
boot from its own partition. This has been changed in the W2K installation
procedure. W2K copies a file named ntfs40.sys to ntfs.sys to the \winnt\drivers
directory of the NT 4.0 system. So what I want to say is: Yes, NT 4.0 has got a
working ntfs.sys driver to see its own partition. The question remains why it
cannot see the W2K partition. Grmbl.
Incidentally, what does windisk think of the partition? I think evenif the ntfs driver isn't loaded, it should properly identify it basedon the partition table. If it doesn't see the whole disk, I wouldensure you have the MS IDE drivers loaded. I've had problems with thePIXIDE drivers not seeing the whole drive and causing missingpartitions.

OK, I have to check that. Just what is windisk and where can it be obtained?

Thanks a lot for taking the trouble. ;-)

Regards,
-Stefan

--
Share what you know, learn what you don't.

** Please make the obvious changes to my address when replying by email.
** Bitte nehmen Sie die offensichtlichen Veränderungen an meiner Adresse vor, wenn Sie per Email antworten.

[Stefan Bischof]

On Sun, 05 Oct 2003 21:24:46 +0200 (CEST), Stefan Bischof wrote:
OK, I have to check that. Just what is windisk and where can it be obtained?

I obviously typed the above message before thinking. Sorry. That's the drive
manager (translation from German to English), right?
Thanks,
-Stefan

--
Share what you know, learn what you don't.

** Please make the obvious changes to my address when replying by email.
** Bitte nehmen Sie die offensichtlichen Veränderungen an meiner Adresse vor, wenn Sie per Email antworten.

[Chris]

On Sun, 05 Oct 2003 21:24:46 +0200 (CEST), "Stefan Bischof"
<nospamplease.stefan.bischof@netic.de> wrote:
On Sat, 04 Oct 2003 16:45:51 GMT, chris@nospam.com wrote:The problem was that the original NT4 system did not have the NTFSdriver running. Try looking under the devices control panel and seeif there is a ntfs driver that is disabled or set to manual.W2K brought a new ntfs.sys to the NT 4.0 system because the W2K installationchanges all present NTFS partitions which it can see to NTFS 5. Two years agothis had the consequence that due to the old ntfs.sys Windows NT 4.0 couldn'tboot from its own partition. This has been changed in the W2K installationprocedure. W2K copies a file named ntfs40.sys to ntfs.sys to the \winnt\driversdirectory of the NT 4.0 system. So what I want to say is: Yes, NT 4.0 has got aworking ntfs.sys driver to see its own partition. The question remains why itcannot see the W2K partition. Grmbl.Incidentally, what does windisk think of the partition? I think evenif the ntfs driver isn't loaded, it should properly identify it basedon the partition table. If it doesn't see the whole disk, I wouldensure you have the MS IDE drivers loaded. I've had problems with thePIXIDE drivers not seeing the whole drive and causing missingpartitions.OK, I have to check that. Just what is windisk and where can it be obtained?


It's the Windows Disk Manager. Just run 'windisk.exe' from
start->run.

-Chris