|
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 > -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.392 / Virus Database: 268.5.5/333 - Release Date: 5/5/2006 -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.