I'm sorry, I stand corrected. I re-unzipped all the files into lowercase
names, and the setup went off without a hitch. Thanks again for all your
help.
On Saturday 03 February 2001 17:36, you wrote:
> That doesn't seem to be it. This error is happening as soon as I run the
> setup program, and it happens (same error, same case (all upper, in fact))
> when I rename SETUP.LST to setup.lst. So it seems it's something else.
> The error message indicates that setup is looking for an invalid file in
> the first place. (See original error message below). Is there a DOS Log
> command I can do to see what file it is really looking for?
>
> Also, when I went in an tried to modify the mapping mode, the OK button was
> greyed out in the dive properties. This happened whether I started
> winsetup as root or as a normal user. Oh well, I gues I'll have to go in
> and sit at the work station and do a CD install.
>
> Thanks for your help.
>
> j----- k-----
>
> On Saturday 03 February 2001 13:46, you wrote:
> > The problem is that "case mapping" is enabled on the J drive.
> > This means that files with upper case filenames must be referenced
> > via the *DOS* filesystem interface via the "mapped" version of the
> > filename, which is what you see. The Windows filesystem interface
> > has less restrictions than the old "8.3" DOS filesystem interface
> > so it does not go thru the same name mapping scheme in Win4Lin.
> > So I guess that what is happening is that the first part of
> > setup uses the DOS filesystem interface to find the files
> > and later uses the windows filesystem interface to read the
> > files. When case mapping is enabled in this scenaio and there
> > are files with upper case characters, then things like this
> > problem will happen. For more on filename mapping issues
> > refer to the user's guide.
> >
> > So you can either change all the filenames to lower case, or
> > use winsetup to turn off case mapping on the J drive.
> >
> > -David
> >
> > "Joshua J. Kugler" wrote:
> > > I just put the contents of the MS Office 97 CD into J:\office97\install
> > > (/var/win4lin/dosroot/office97/install). I zipped the CD, then unzip'ed
> > > the contents to the directory. Directories have permissions 755, files
> > > have 644. When I try to run setup, I get this message:
> > >
> > > Setup cannot access the required initialization file:
> > > 'J:\OFFICE97\INSTALL\SET'8V4X.LST'
> > >
> > > Yes, that extra apostrophe is in there. There is a SETUP.LST file, but
> > > not the file it thinks it's looking for. It looks like some kind of
> > > character set issue. Does anyone have any ideas about this? I haven't
> > > been able to try an install from the CD as I'm working remotely at the
> > > moment; would that make a difference?
> > >
> > > Thanks for any help you can give.
> > >
> > > Thanks for a great product, Netraverse! I just purchased a license so
> > > I can support Windows users and do development on Access databases
> > > (with a MySQL back end, of course. :).
> > >
> > > j----- k-----
> > >
> > > --
> > > Joshua Kugler
> > > Associated Students of the University of Alaska Fairbanks
> > > Information Services Director
> > > [EMAIL PROTECTED]
> > > 907-474-7601
> > > _______________________________________________
> > > Win4Lin-users mailing list
> > > [EMAIL PROTECTED]
> > > https://lists.netraverse.com/mailman/listinfo/win4lin-users
> >
> > _______________________________________________
> > Win4Lin-users mailing list
> > [EMAIL PROTECTED]
> > https://lists.netraverse.com/mailman/listinfo/win4lin-users
--
Joshua Kugler
Associated Students of the University of Alaska Fairbanks
Information Services Director
[EMAIL PROTECTED]
907-474-7601
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
