Re: Win2003 install BSOD on IXS -- MIDRANGE-L

Hi Richard,

I think that statement is right or wrong depending upon which version ofOS400 you're on. On a V4R4 system (like the one right under my table atthe moment) IBM did some strange stuff with the Windows installatiion onthe IXS card. It has Windows NT 4.0 Server on it, with a C: (FAT), D:(FAT) and E: (NTFS) drive on it. The C: drive is the boot drive, the D:drive has install files on it, and the E: drive has Windows on it. TheC: drive is a whopping 10MB; D: is 200MB; E: is 1GB. All these werecreated by the install process. C: apparently is only used to boot; D:has some Windows installation files; and E: has the installed Windows NT4.0 Server os on it.

When I did the same install on a V5R2 machine, it ended up with only aC: (NTFS) and D: (don't remember, possibly FAT) drives -- C: containedthe Windows os and the boot software; D: contained the Windowsinstallation files.

In both cases, the install allowed choosing which format the Windowsdrive would use, FAT or NTFS. The other drives' formats were chosen bythe install process.


*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
pdow@xxxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxxx> /

richard@xxxxxxxxxxx wrote:

In regards to the not booting unless the boot drive it FAT or FAT32, Ithink that statement is wrong.I have installed the IXS with both Windows 2000 Server and Windows 2003Server and each time the primary drive was NTFS.I'm thinking you might need to start with a regular Windows 2003 CDinstead of the SBS load.
Just a thought :-)

Regards,
Richard Schoen
RJS Software Systems Inc."Providing Your....iNFORMATION NOW!"
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 898-3038
Fax: (952) 898-1781
Toll Free: (888) RJSSOFT
------------------------------

message: 6
date: Fri, 5 May 2006 16:15:39 -0400
from: "Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx>
subject: RE: Win2003 install BSOD on IXS
Something to do with what drivers are loaded when.
I do know it will not boot if the boot drive is converted to ntfs.
Ouch! I consider that a major drawback, and would probably fail a server
if I was doing a security audit on it. A well secured server has NTFS on
the boot drive and most services running as non-privileged users so
there's no way to corrupt/infect the boot disk. Hard to mess up xxx.dll
when you don't have write access to it. <G>

-Walden