[Unattended] Any one got drivers installed from ATI Rage pro or the like graphics card

2004-03-31 Thread Max Lovius
Title: Any one got drivers installed from ATI Rage pro or the like graphics card I have a few computers that have these old ATI Rage 128 pro, they are quite old so I don't want so spend time on this, but I have failed to find a way to install the drives ATI provide, which are applications

[Unattended] error running make images

2004-03-31 Thread TUSSEY Aloha
This is what i get: Making images/b44.imz...Bad media types ff/f0, probably non-MSDOS disk Cannot initialize 'X:' Bad target x:/./autoexec.bat Bad media types ff/f0, probably non-MSDOS disk Cannot initialize 'X:' Bad target x:/./choice.exe Bad media types ff/f0, probably non-MSDOS disk Cannot

RE : [Unattended] Any one got drivers installed from ATI Rage pro or the like graphics card

2004-03-31 Thread Sylvain Faivre
Title: Message Hello, This is what i've done, but i'm not quite sure it installs everything you want. Maybe some of the ATI tools are not installed this way, but i don't care much as long as the drivers work. Let me know ifthat works for you. Get the official ATI driversand extract their

Re: [Unattended] error running make images

2004-03-31 Thread Patrick J. LoPresti
TUSSEY Aloha [EMAIL PROTECTED] writes: This is what i get: Making images/b44.imz...Bad media types ff/f0, probably non-MSDOS disk More information, please. Is this under Linux, Cygwin, or something else? What version of mtools? - Pat

Re: [Unattended] error running make images

2004-03-31 Thread Eugene Kotlyarov
TUSSEY Aloha wrote: This is what i get: Making images/b44.imz...Bad media types ff/f0, probably non-MSDOS disk Cannot initialize 'X:' Bad target x:/./autoexec.bat Bad media types ff/f0, probably non-MSDOS disk Cannot initialize 'X:' Bad target x:/./choice.exe Bad media types ff/f0, probably

RE: RE : [Unattended] Any one got drivers installed from ATI Rage pro or the like graphics card

2004-03-31 Thread Max Lovius
Thanks, That one I think was my mistake on both counts... I was using an old installation and had the wrong path in the OemPnPDriversPath (made by hand), just goes to prove you should use the unattended as that would not have happened, if it had been a 100% an unattended installation. Sorry for

Re: [Unattended] error running make images

2004-03-31 Thread Eugene Kotlyarov
TUSSEY Aloha wrote: This is what i get: Making images/b44.imz...Bad media types ff/f0, probably non-MSDOS disk Cannot initialize 'X:' Bad target x:/./autoexec.bat Bad media types ff/f0, probably non-MSDOS disk Cannot initialize 'X:' I suppose you install Cygwin with Default text file type

Re: [Unattended] error running make images

2004-03-31 Thread Patrick J. LoPresti
Eugene Kotlyarov [EMAIL PROTECTED] writes: I suppose you install Cygwin with Default text file type option set to DOS, you should reinstall it with Default text file type set to Unix. This is my guess for the problem, too. But you should not need to reinstall Cygwin. Instead, just set the

RE: [Unattended] Sharing unattended install scripts

2004-03-31 Thread Jeff Black
Subject: [Unattended] Sharing unattended install scripts I am interested in submitting scripts for installing other applications. In a recent message on the unattended-devel list (http://sourceforge.net/mailarchive/message.php?msg_id=7594763), Pat suggested uploading to a public website

RE: [Unattended] Sharing unattended install scripts

2004-03-31 Thread Don Morrison
In an ideal world, should all unattended users be adding their scripts to the main unattended distribution, or is it desirable to keep the included set of scripts to some limited, manageable set? Personally, I'd like to see a /contrib. directory with optional scripts. The scripts