Re: Win2003 install BSOD on IXS

The info I was using came from the Windows Integration book 
(sg24659 http://www.redbooks.ibm.com/abstracts/sg246959.html )

On page 37.

<snip>
The D: drive can be up to 2047 MB in size and must remain formatted as 
FAT. The 
INSWNTSVR command increases the size of your D: drive to 762 MB if you 
enter anything 
less than that.
</snip>

and page 119:
<snip>
Disk 1 was created with the INSWNTSVR command. This disk, usually the D: 
drive, must 
remain a Basic, FAT format disk. When your server is varied on, a file 
called QVNDCFG.TXT 
is copied to the root of Disk 1. This file is used to connect the Windows 
server?s iSeries 
Integrated services to the iSeries? Windows server administration job 
running in the 
QSYSWRK subsystem on the iSeries. If you convert the disk, the file cannot 
be written to the 
drive and your server will fail to vary on.
</snip>


So it look like I was right and wrong.  If the install drive is converted 
to NTFS
the server will not very on.  It will not give you the BSOD


_____________________________
Bryan Dietz 
Aktion Associates 


midrange-l-bounces@xxxxxxxxxxxx wrote on 05/06/2006 05:41:13 PM:

-> The point is moot, as the problem was that some PTFs were not 
-> installed - of course, why should something be released that needs a 
-> fix before it can be used? Oh, that's right,  I am not to ask that 
-> kind of question, am I?
-> 
-> 
-> At 03:40 PM 5/6/2006, you wrote:
-> 
-> >Hi Richard,
-> >
-> >I think that statement is right or wrong depending upon which version 
of
-> >OS400 you're on.  On a V4R4 system (like the one right under my table 
at
-> >the moment) IBM did some strange stuff with the Windows installatiion 
on
-> >the 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. The
-> >C: drive is a whopping 10MB; D: is 200MB; E: is 1GB.  All these were
-> >created by the install process.  C: apparently is only used to boot; 
D:
-> >has some Windows installation files; and E: has the installed Windows 
NT
-> >4.0 Server os on it.
-> >
-> >When I did the same install on a V5R2 machine, it ended up with only a
-> >C: (NTFS) and D: (don't remember, possibly FAT) drives -- C: contained
-> >the Windows os and the boot software; D: contained the Windows
-> >installation files.
-> >
-> >In both cases, the install allowed choosing which format the Windows
-> >drive would use, FAT or NTFS.  The other drives' formats were chosen 
by
-> >the 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, I
-> > > think that statement is wrong.
-> > >
-> > > I have installed the IXS with both Windows 2000 Server and Windows 
2003
-> > > Server and each time the primary drive was NTFS.
-> > >
-> > > I'm thinking you might need to start with a regular Windows 2003 CD
-> > > instead 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
-> > >
-> >

->