Some questions about NT...

[Jestermask]

So, my apologies for the ignorance on the subject...

1) NT is based on Win95? If that is the case, can something that works with Win98se (i.e. a CD-RW drive) work with NT?

2) If that's possible, what CD burning software would work with NT? Again, could something that's compatible with Win98se?

Thanks for the help in advance! :D

~JM

[Jesse Carlton]

nt isn't based on win 95, it's based on a kernel adapted from windows for workgroups.

[Jestermask]

Okay, so then what would I look for in terms of compatibility if something doesn't specifically say it's made for NT?

[Jesse Carlton]

if it says it's compatible with win 95, 98 or 2000 it should be with nt

2000 is basically just a newer version of nt, and xp is built on that.

[Rudy]

Okay, so then what would I look for in terms of compatibility if something doesn't specifically say it's made for NT?

585809054[/snapback]

it might work but it might not, what version of NT are you installing?? if its NT4 then maybe but if its 2000 then most likely

[markwolfe Veteran]

You can check if specific hardware is officially suppoted on Microsoft's website:

http://support.microsoft.com/?kbid=131303

EDIT: Odd... it says for NT, but they don't list NT any more... :ermm:

EDIT#2: nevermind. It has been moved to "legacy". Direct link: https://winqual.microsoft.com/download/hcl/NT40xHCL.txt

Edited April 21, 2005 by markjensen

[TheWahbinator]

nt isn't based on win 95, it's based on a kernel adapted from windows for workgroups.

585809026[/snapback]

I hope you mean OS/2?

[dougal.s]

NT was a more network orientated version of the Windows OS. Had nothing to do with OS2 afaik.

Dougal.

[Lurchybaby]

NT was NOTORIOUSLY picky about hardware. Just because something worked with 95/98/2000 does NOT mean it will work with NT 3.x/4.

the stuff being flung about in this thread is making me laugh.

[TheWahbinator]

NT was a more network orientated version of the Windows OS. Had nothing to do with OS2 afaik.

585810377[/snapback]

Okay, maybe just the concept of it.

[Angel Blue01]

No.

OS/2 was the original project. It was part of IBM and Microsoft. Then Microsoft spun off and formed NT -after the N-Ten.

[Brandon Live Veteran]

Windows NT was developed to beat OS/2 and compete with Unix server and workstation systems.

Windows NT has no relation to Windows For Workgroups.

Windows NT was built by several of the original OpenVMS designers. NT employs many VMS design concepts.

NT was designed to bring the following to the Windows platform:

1) A new, non-DOS based platform

2) Unix-style file/folder permissions

3) A clear seperation of kernel space and user space. This improves stability and reliability.

4) NT was built from the ground up for threaded operation.

NT was built to support a variety of architectures (as opposed to just x86 which was all that DOS and Windows 3.x supported).

NT was built to support any number of user-space system implementations, which they call "subsystems." Theses subsystems sit on top of the NT microkernel much like the FreeBSD user space sits atop the Mach microkernel on Apple's OS X.

Examples of supported NT OS subsystems include: Win32, POSIX, OS/2, and Interix/SFU.

Micrsooft built Win32 as a common high-level API that would be supported on both NT and Windows 3.x/9x systems. This allowed developers (to some extent) to be able to write an application for one platform and have it work on the others, even though Win32 is not the native API for NT.

[GAM]

So, my apologies for the ignorance on the subject...

1) NT is based on Win95?

No, it is not. It is more based on OS/2 when it comes to the core OS parts, allthough some user mode programs that shipped with the OS was based on the same or similar apps in Windows 98.

If that is the case, can something that works with Win98se (i.e. a CD-RW drive) work with NT?

It is not the case. Something that works with Windows 98se may work with NT, but please note that NT had a very different driver model than 98se. It is very likely that anything requiring a device driver is going to have issues on NT, and may flat out NOT work. Windows 2000 on the other hand re-adopted the 98-style device driver model, so you have better luck finding a match there.

2) If that's possible, what CD burning software would work with NT? Again, could something that's compatible with Win98se?

I don't know the answer to that one, but you may want to spend some time at Google's site to see if you can find something.

My advice would be to forget about 98se and NT, and get a more modern OS --if cost is an issue then consider Linux or FreeBSD for example....

[jjackson02]

Windows NT was developed to beat OS/2 and compete with Unix server and workstation systems.

Windows NT has no relation to Windows For Workgroups.

Windows NT was built by several of the original OpenVMS designers.  NT employs many VMS design concepts. 

NT was designed to bring the following to the Windows platform:

1) A new, non-DOS based platform

2) Unix-style file/folder permissions

3) A clear seperation of kernel space and user space.  This improves stability and reliability.

4) NT was built from the ground up for threaded operation.

NT was built to support a variety of architectures (as opposed to just x86 which was all that DOS and Windows 3.x supported). 

NT was built to support any number of user-space system implementations, which they call "subsystems."  Theses subsystems sit on top of the NT microkernel much like the FreeBSD user space sits atop the Mach microkernel on Apple's OS X.

Examples of supported NT OS subsystems include: Win32, POSIX, OS/2, and Interix/SFU.

Micrsooft built Win32 as a common high-level API that would be supported on both NT and Windows 3.x/9x systems.  This allowed developers (to some extent) to be able to write an application for one platform and have it work on the others, even though Win32 is not the native API for NT.

585810443[/snapback]

Finally!! Someone who knows what they're talking about! :D