🚀 go-pugleaf

"blah" <bl...@blah.com> wrote in message
news:b1ndu6$h0n$1@gnamma.connect.com.au...
> I'm trying to get Privateer to work (again) under Win98SE.  I've made a
boot
> disk and a FAT16 drive D, and installed the game to the FAT16 drive.  The
> boot disk fails because EMM386 doesn't like the code page option
specified.
> I used the one from the help file on the CD.

FWIW the exact error message from EMM386 is "Unable to set page frame base
address.  EMS unavailable."

Microsoft suggest using MSD to find out what is occupying memory - which is
fine if you are running a full install of DOS but useless in Win98SE where
MSD doesn't exist in the DOS shell.

I tried a DOS 6.22 boot disk from www.bootdisk.com but ended up at a DOS
prompt that listed any drive higher than B as invalid.

PRIV.EXE refuses to run without EMS.

Rob

In article <b1nnm6$lcq$1...@gnamma.connect.com.au>, blah <bl...@blah.com> wrote:
>
>"blah" <bl...@blah.com> wrote in message
>news:b1ndu6$h0n$1@gnamma.connect.com.au...
>> I'm trying to get Privateer to work (again) under Win98SE.  I've made a
>boot
>> disk and a FAT16 drive D, and installed the game to the FAT16 drive.  The
>> boot disk fails because EMM386 doesn't like the code page option
>specified.
>> I used the one from the help file on the CD.
>
>FWIW the exact error message from EMM386 is "Unable to set page frame base
>address.  EMS unavailable."
>
>Microsoft suggest using MSD to find out what is occupying memory - which is
>fine if you are running a full install of DOS but useless in Win98SE where
>MSD doesn't exist in the DOS shell.
>
>I tried a DOS 6.22 boot disk from www.bootdisk.com but ended up at a DOS
>prompt that listed any drive higher than B as invalid.
>
>PRIV.EXE refuses to run without EMS.

Try adding: "DRIVES=H" to your config.sys on the bootdisk (without the
quotes, of course). That should let you access higher drives.

Or are all your drives FAT-32?

One thing that also works - grab "FAKECD" and run that to make it think your
hard drive directory is really a CD. As I recall, that works quite well for
priv.

I have a working config somewhere. Let me know if you need it, and I'll dig
it up.

Mattias

"Mattias Hembruch" <mghe...@ecexh.uwaterloo.ca> wrote in message
news:b1p1pu$q2u$1@tabloid.uwaterloo.ca...
> >PRIV.EXE refuses to run without EMS.
> Try adding: "DRIVES=H" to your config.sys on the bootdisk (without the
> quotes, of course). That should let you access higher drives.

Do you mean "lastdrive=h"?

> Or are all your drives FAT-32?

No, I created the D: drive as a 500MB FAT16 drive especially for privateer.

> One thing that also works - grab "FAKECD" and run that to make it think
your
> hard drive directory is really a CD. As I recall, that works quite well
for
> priv.

The DOS boot disk was able to see the CDROM drive but it couldn't see any of
the hard drives.  Thanks for the suggestions though.

> I have a working config somewhere. Let me know if you need it, and I'll
dig
> it up.

I'd appreciate it, thanks!  I am beginning to suspect that the Motherboard
I/O and the PCI SCSI card are using up all the UMB for I/O ports.  I looked
in MSINFO in Win2K and that is what seems to be happening.  I am not sure
how much of the UMB's EMM386 needs to use high memory for EMS.

Rob

blah wrote:
> I'm trying to get Privateer to work (again) under Win98SE.  I've made a boot
> disk and a FAT16 drive D, and installed the game to the FAT16 drive.  The
> boot disk fails because EMM386 doesn't like the code page option specified.
> I used the one from the help file on the CD.  Does anyone have any
> config.sys files and autoexec.bat files they've used successfully to get
> Privateer to run?

This isn't by chance a laptop, is it? From this post (and your next one) 
it is evident what your problem is: EMM needs 64k HMA in order to work. 
Your PC does not have such a window free (or at least it doesn't have a 
64k block free). This usually happens if you have a PCMCIA drive and/or 
you have a huge BIOS (usually with 'useless' energy saving routines).

Try to find out what clutters up your HMA (post it).
Maybe you can disable some stuff in the BIOS?
My suggestion would be to use the I=XXXX-XXXX parameter of EMM386 in 
order to forceinclude some 64k block. I do so for my laptop (E000-EFFF 
IIRC) which is actually overwriting some part of the BIOS for me.
Beware, trying this might could to a lot of weird problems, like erasing 
your HD, so backup before trying...

--
Artificial Intelligence usually beats real stupidity.

[Delete the karl after the @ to avoid my spam trap]

Privateer, Strike Commander, WC1&2, all use a protected memory mode that 
cannot be emulated by win98se.  So your solution to use a boot disk with 
Dos 6.22 is the way to go.

Is your D drive a Primary or Logical partition?  

Don't try playing with codepages, memory ranges, and driver jockying 
trying to get the needed dos ram.  Search the web for QEMM 97, you can 
download the whole thing.  Qemm is an old memory manager that even with 
all types of DOS drivers loaded will still give you over 600k free.  It 
was a must-have in the dos days.

Also note that if your Sound Card is PCI, then it won't work under DOS, 
nor its game port.

The best bet is to do what I just did.  I was spending days working on 
configurations to get these dos games to run, just to have them play way 
too fast on my P4 system. (Privateer-2 even played too fast on an old p2-
300 laptop).  You can buy a complete P200mmx system for about $30 from 
ebay.  Set this pc up for dual boot with DOS and Windows98se.  It will 
play all these dos programs fine, and all the older WC series windows 
games (kilrathi saga, Privateer 2, WC 4....).  I can use my older CH 
gameport gear for the DOS sessions, and my TM Cougar for the win98se 
sessions.  Much better option for my sanity :)



"blah" <bl...@blah.com> wrote in news:b1ndu6$h0n$1...@gnamma.connect.com.au:

> I'm trying to get Privateer to work (again) under Win98SE.  I've made
> a boot disk and a FAT16 drive D, and installed the game to the FAT16
> drive.  The boot disk fails because EMM386 doesn't like the code page
> option specified. I used the one from the help file on the CD.  Does
> anyone have any config.sys files and autoexec.bat files they've used
> successfully to get Privateer to run?
> 
> Rob
> 
> 

On 6 Feb 2003 05:15:39 GMT, in alt.games.wing-commander scatter
<sca...@nospam.com> wrote:

>Privateer, Strike Commander, WC1&2, all use a protected memory mode that 
>cannot be emulated by win98se. 

No...  Wing Commander 1 and 2 run quite happily in a window in Windows 9x if set
up properly.  Privateer does not, as JEMM won't work with Windows.  I've never
tried to run Strike Commander in Windows.

Karl Frank wrote:

> My suggestion would be to use the I=XXXX-XXXX parameter of EMM386 in 
> order to forceinclude some 64k block. I do so for my laptop (E000-EFFF 
> IIRC) which is actually overwriting some part of the BIOS for me.
> Beware, trying this might could to a lot of weird problems, like erasing 
> your HD, so backup before trying...

I should add: When I say overwriting of the BIOS I mean the copy of the 
BIOS in the RAM. No harm will be done to the BIOS. Due to the missing 
procedures your PC can however do stupid stuff that is why your HD data 
might be in danger.

--
Duct tape is like the force, it has a light side and a
dark side and it holds the universe together.

[Delete the karl after the @ to avoid my spam trap]

"scatter" <sca...@nospam.com> wrote in message
news:b1sr1r$b1d$1@bob.news.rcn.net...
> Privateer, Strike Commander, WC1&2, all use a protected memory mode that
> cannot be emulated by win98se.  So your solution to use a boot disk with
> Dos 6.22 is the way to go.
> Is your D drive a Primary or Logical partition?

Logical.  But then, the boot disk couldn't see C either, and that's a
primary (FAT32) drive.

> Also note that if your Sound Card is PCI, then it won't work under DOS,
> nor its game port.

It's on the motherboard, but it identifies itself as as an SBPCI

> 300 laptop).  You can buy a complete P200mmx system for about $30 from
> ebay.  Set this pc up for dual boot with DOS and Windows98se.

I'll have to get my old machine back from the friend who borrowed it.
Unfortunately that has an onboard SCSI controller so it may have similar
hassles but at least I can disable it!!  Sounds to me like this is the
option I'll have to take.

No point me buying anything off ebay - I'm in Australia! ;)
(and yes I do know there's an ebay.com.au)

Rob

"Karl Frank" <ka...@karl.frank.name> wrote in message
news:964956305.373648@news.ainet.at...
> This isn't by chance a laptop, is it? From this post (and your next one)
> it is evident what your problem is: EMM needs 64k HMA in order to work.
> Your PC does not have such a window free (or at least it doesn't have a
> 64k block free). This usually happens if you have a PCMCIA drive and/or
> you have a huge BIOS (usually with 'useless' energy saving routines).

Hi Karl!  No, it's not a laptop.  It's a desktop PC with a Gigabyte
motherboard that has standard IDE interfaces, plus a Promise RAID
controller, plus memory stick, smartcard, who knows what else, and the PCI
SCSI card also appears to have claimed a lot of the upper memory.

> Maybe you can disable some stuff in the BIOS?

No, there's no settings to determine which memory the I/O devices use, and I
do need the SCSI and RAID controllers.  So I don't think there's anything I
can actually disable without unplugging my scanner and my RAID stack.

Thanks for the suggestions.  Someone else suggested getting an old machine
and using that - I have an older PC at a friend's place, and at this point I
think it would be easier to get it to work than to battle with trying to run
a DOS game on the PIV I'm using now!

The point which made me decide this direction was that the onboard soundcard
probably wouldn't work in DOS.

Rob

In article <b1te8u$dca$1...@gnamma.connect.com.au>, blah <bl...@blah.com> wrote:
>"Karl Frank" <ka...@karl.frank.name> wrote in message
>news:964956305.373648@news.ainet.at...
>> This isn't by chance a laptop, is it? From this post (and your next one)
>> it is evident what your problem is: EMM needs 64k HMA in order to work.
>> Your PC does not have such a window free (or at least it doesn't have a
>> 64k block free). This usually happens if you have a PCMCIA drive and/or
>> you have a huge BIOS (usually with 'useless' energy saving routines).
>
>Hi Karl!  No, it's not a laptop.  It's a desktop PC with a Gigabyte
>motherboard that has standard IDE interfaces, plus a Promise RAID
>controller, plus memory stick, smartcard, who knows what else, and the PCI
>SCSI card also appears to have claimed a lot of the upper memory.

You might be able to turn of video bios shadowing, etc.. not sure if that
frees up "upper memory" though.


>> Maybe you can disable some stuff in the BIOS?
>
>No, there's no settings to determine which memory the I/O devices use, and I
>do need the SCSI and RAID controllers.  So I don't think there's anything I
>can actually disable without unplugging my scanner and my RAID stack.
>
>Thanks for the suggestions.  Someone else suggested getting an old machine
>and using that - I have an older PC at a friend's place, and at this point I
>think it would be easier to get it to work than to battle with trying to run
>a DOS game on the PIV I'm using now!
>
>The point which made me decide this direction was that the onboard soundcard
>probably wouldn't work in DOS.

Good call. Slim chance of that.

Mattias

In article <b1sr1r$b1d$1...@bob.news.rcn.net>,
scatter  <sca...@nospam.com> wrote:
>Privateer, Strike Commander, WC1&2, all use a protected memory mode that 
>cannot be emulated by win98se.  So your solution to use a boot disk with 
>Dos 6.22 is the way to go.

Well, that, or just set "MULTIBOOT=1" and "GUI=0" in msdos.sys (think that's
the parameter) for 98SE and boot just into DOS "7.0"..

Mattias

"Mattias Hembruch" <mghe...@ecexh.uwaterloo.ca> wrote in message
news:b1uruq$r1q$1@tabloid.uwaterloo.ca...
> Well, that, or just set "MULTIBOOT=1" and "GUI=0" in msdos.sys (think
that's
> the parameter) for 98SE and boot just into DOS "7.0"..

Wouldn't that be the same as holding down F8 and choosing DOS from the boot
menu?

Rob

blah wrote:

>>Well, that, or just set "MULTIBOOT=1" and "GUI=0" in msdos.sys (think
>>the parameter) for 98SE and boot just into DOS "7.0"..
> Wouldn't that be the same as holding down F8 and choosing DOS from the boot
> menu?

Without the multiboot=1 you won't get the option of holding F8.
If you do GUI=1 I think it defaults to DOS and you have to press F( to 
get to Windows. Not sure.

--
    /\       Karl FRANK
   /  \      e-mail: karl(at)frank(dot)name
  /\  /\     WWW   : http://www.karl.frank.name
/ \\// \    PGP-Fingerprint: CC2B 8E55 D9F8 5DEC 814C  2E64 6419 D357 
59A0 02EE
	
[Delete the karl after the @ to avoid my spam trap]

In article <96515307...@news.ainet.at>,
Karl Frank  <ka...@karl.frank.name> wrote:
>blah wrote:
>
>>>Well, that, or just set "MULTIBOOT=1" and "GUI=0" in msdos.sys (think
>>>the parameter) for 98SE and boot just into DOS "7.0"..
>> Wouldn't that be the same as holding down F8 and choosing DOS from the boot
>> menu?
>
>Without the multiboot=1 you won't get the option of holding F8.
>If you do GUI=1 I think it defaults to DOS and you have to press F( to 
>get to Windows. Not sure.

No, if you do GUI=0, it defaults to DOS, and you type "win" to get to win.

I think if you set GUI=1, it will boot win, but not without giving you a
chance to stop in DOS, or something like that..

Mattias

"blah" <bl...@blah.com> wrote in message
news:b1qoev$5e3$1@gnamma.connect.com.au...

> I'd appreciate it, thanks!  I am beginning to suspect that the Motherboard
> I/O and the PCI SCSI card are using up all the UMB for I/O ports.  I
looked
> in MSINFO in Win2K and that is what seems to be happening.  I am not sure
> how much of the UMB's EMM386 needs to use high memory for EMS.
>
> Rob
>

PCI SCSI?  Your hard drive, is it SCSI too?  Are you loading the ASPIx
drivers on your boot disk?  If not, then your DOS cannot see the hard drives
to be able to work with them.

-thehawk

"thehawk" <thehaw...@hotmaildot.com> wrote in message
news:ww11a.31336$be.19210@rwcrnsc53...
>
> "blah" <bl...@blah.com> wrote in message
> news:b1qoev$5e3$1@gnamma.connect.com.au...
>
> > I'd appreciate it, thanks!  I am beginning to suspect that the
Motherboard
> > I/O and the PCI SCSI card are using up all the UMB for I/O ports.  I
> looked
> > in MSINFO in Win2K and that is what seems to be happening.  I am not
sure
> > how much of the UMB's EMM386 needs to use high memory for EMS.
> >
> > Rob
> >
>
> PCI SCSI?  Your hard drive, is it SCSI too?  Are you loading the ASPIx
> drivers on your boot disk?  If not, then your DOS cannot see the hard
drives
> to be able to work with them.
>
> -thehawk
>
I read thru some other of your posts in the other branches in your thread;
are your hard drive(s) perhaps plugged into your RAID controller?  Again,
the DOS needs to have drivers loaded into the CONFIG.SYS and possibly the
AUTOEXEC.BAT files before it can work with the controller to be able to see
the drive(s) on the other side of it.

-thehawk

blah wrote:

>  I am not sure
> how much of the UMB's EMM386 needs to use high memory for EMS.

64k, but but it has to be in one block.

--
There's a story about the military pilot calling for a priority
landing because his single-engine jet fighter was running "a bit
peaked". ATC told the fighter jock that he was number two behind
a B-52 that had one engine shut down. "Ah", the pilot remarked,
"the dreaded seven-engine approach".

[Delete the karl after the @ to avoid my spam trap]

thehawk wrote:

> PCI SCSI?  Your hard drive, is it SCSI too?  Are you loading the ASPIx
> drivers on your boot disk?  If not, then your DOS cannot see the hard drives
> to be able to work with them.

Not true. Harddrives don't need a driver.

--
There's a story about the military pilot calling for a priority
landing because his single-engine jet fighter was running "a bit
peaked". ATC told the fighter jock that he was number two behind
a B-52 that had one engine shut down. "Ah", the pilot remarked,
"the dreaded seven-engine approach".

[Delete the karl after the @ to avoid my spam trap]

"Karl Frank" <ka...@karl.frank.name> wrote in message
news:965209702.443947@news.ainet.at...
> thehawk wrote:
>
> > PCI SCSI?  Your hard drive, is it SCSI too?  Are you loading the ASPIx
> > drivers on your boot disk?  If not, then your DOS cannot see the hard
drives
> > to be able to work with them.
>
> Not true. Harddrives don't need a driver.
>

True, hard drives do not need drivers.  However, if the controller they are
plugged into happens to be something besides an IDE controller, then your
DOS needs a driver in order to use that controller, and to see the drives
plugged into it.

-thehawk

thehawk wrote:
>>Not true. Harddrives don't need a driver.
> True, hard drives do not need drivers.  However, if the controller they are
> plugged into happens to be something besides an IDE controller, then your
> DOS needs a driver in order to use that controller, and to see the drives
> plugged into it.

Again, no - they don't.
I had an Adaptec 2940, 2940U and 2940AU in my systems and _NONE_ needed 
a driver for the HDs to work. I don't have any IDE devices in there so 
I'd have a hard time booting my machine if you were correct...
If course you need a driver to access CD drives or Zip drives. But the 
PCI card adds its own BIOS in the boot process, enough to work as long 
as only HDs are needed... I heared that only 2 HDs work wothut driver, 
but as I got 3 I can deny that rumor...

--
The following is a new Windows message that is under consideration for 
the planned Windows 2001:
* BREAKFAST.SYS halted... Cereal port not responding.


[Delete the karl after the @ to avoid my spam trap]

"Karl Frank" <ka...@karl.frank.name> wrote in message
news:965324301.645397@news.ainet.at...
> thehawk wrote:
> >>Not true. Harddrives don't need a driver.
> > True, hard drives do not need drivers.  However, if the controller they
are
> > plugged into happens to be something besides an IDE controller, then
your
> > DOS needs a driver in order to use that controller, and to see the
drives
> > plugged into it.
>
> Again, no - they don't.
> I had an Adaptec 2940, 2940U and 2940AU in my systems and _NONE_ needed
> a driver for the HDs to work. I don't have any IDE devices in there so
> I'd have a hard time booting my machine if you were correct...
> If course you need a driver to access CD drives or Zip drives. But the
> PCI card adds its own BIOS in the boot process, enough to work as long
> as only HDs are needed... I heared that only 2 HDs work wothut driver,
> but as I got 3 I can deny that rumor...
>

It all depends on your operating system, (or disk operating system), I work
on them all the time.  For example, all of our servers have Adaptec 2940's
of various flavors in them.  We use W2K Server as the operating system, and
we use Symantec Ghost (which is DOS based, as opposed to Windows based) to
create a disk image of them, so as to reduce the amount of reinstalls.  One
can NOT create an image of those drives without loading the ASPI drivers for
the controller card in the CONFIG.SYS first.

You are absolutely correct in that the SCSI controller has a BIOS, which
tells the machine itself how to work with the hardware, but it does not
necessarily tell your operating system how to work with it.  If that were
the case, then there would be no need for the whole "press F3 (or F6 I
think, depending on your flavor of windows) to load additional mass storage"
type drivers before you can install the NT based Windows operating systems.

I still have a system around here with an Adaptec 2940UW in it, which has
Red Hat on it at the moment.  I'll give it a format (and change the file
system back, and alla that) and see what happens and come back and talk some
more.

Our discussion aside, has Blah ever had the original question answered?  And
if so, what was the answer (I have looked thru the other branches of this
thread, and am not seeing if a resolution was reached)?

-thehawk

thehawk wrote:

> It all depends on your operating system, (or disk operating system), I work
> on them all the time.  For example, all of our servers have Adaptec 2940's
> of various flavors in them.  We use W2K Server as the operating system, and
> we use Symantec Ghost (which is DOS based, as opposed to Windows based) to
> create a disk image of them, so as to reduce the amount of reinstalls.  One
> can NOT create an image of those drives without loading the ASPI drivers for
> the controller card in the CONFIG.SYS first.

That is interesting. As I backup on a streamer or CDRWs and thus not 
doing a pyhsical image I never encountered that. For normal applications 
the bios seems to be enough, but I know ASPI provides enhanced 
functions. Looks like that is one of them.

> Our discussion aside, has Blah ever had the original question answered?  And
> if so, what was the answer (I have looked thru the other branches of this
> thread, and am not seeing if a resolution was reached)?

I don't think so. He resorted to get another machine IIRC. There really 
isn't that much that we can do for him either besides suggesting to 
disable hardware or try to force back memory from them.

--
WINDOOF-MANAGER-ERROR:
Lassen Sie es mich einmal so ausdrücken...

[Delete the karl after the @ to avoid my spam trap]

"Karl Frank" <ka...@karl.frank.name> wrote in message
news:965382857.624658@news.ainet.at...
> thehawk wrote:
> > Our discussion aside, has Blah ever had the original question answered?
And
> > if so, what was the answer (I have looked thru the other branches of
this
> > thread, and am not seeing if a resolution was reached)?
> I don't think so. He resorted to get another machine IIRC. There really
> isn't that much that we can do for him either besides suggesting to
> disable hardware or try to force back memory from them.

As far as I can make out, it's impossible to run Privateer on my P4.  The
UMB is being used by the SCSI BIOS, the RAID BIOS and various other I/O
devices which I can't move.  Using another PC is really my only option.  I
only hope my older motherboard allows me to free the UMB.  Since it is also
a Gigabyte board and has onboard SCSI, I'm dubious.

Thanks for the suggestions though!

Rob

blah wrote:

> As far as I can make out, it's impossible to run Privateer on my P4.  The
> UMB is being used by the SCSI BIOS, the RAID BIOS and various other I/O
> devices which I can't move.  Using another PC is really my only option.  I
> only hope my older motherboard allows me to free the UMB.  Since it is also
> a Gigabyte board and has onboard SCSI, I'm dubious.

One more thing to try:
device=a:\emm386.exe /i=b000-b7ff

the memory between b000 and b7ff isn't exactly much (32k), but maybe 
enough to get a full 64k block if only a few k are missing.
I don't know what is in there - either bios commands for advanced text 
output or for monocrome graphics IIRC. Nothing very important while 
gaming anyhow ;)

--
Better to understand a little than to misunderstand a lot.

[Delete the karl after the @ to avoid my spam trap]

"Karl Frank" <ka...@karl.frank.name> wrote in message
news:965483201.315784@news.ainet.at...
> One more thing to try:
> device=a:\emm386.exe /i=b000-b7ff

According to MSInfo in Win2K, B000-B03F is used by the Soundblaster,
B400-BC07 is used by the RAID device.  Both are on the motherboard and short
of totally disabling them, I can't do anything about their memory usage.
Two more blocks in the C000-CFFF range are used by the Promise interface,
then above that is the USB controller I/O and the standard IDE interface.

I'll just have to get hold of the old computer and with it I CAN disable
devices like the SCSI which I am not using.

Rob

On Thu, 6 Feb 2003 20:39:33 +1000, in alt.games.wing-commander "blah"
<bl...@blah.com> wrote:

>"scatter" <sca...@nospam.com> wrote in message
>news:b1sr1r$b1d$1@bob.news.rcn.net...
>> Privateer, Strike Commander, WC1&2, all use a protected memory mode that
>> cannot be emulated by win98se.  So your solution to use a boot disk with
>> Dos 6.22 is the way to go.
>> Is your D drive a Primary or Logical partition?
>
>Logical.  But then, the boot disk couldn't see C either, and that's a
>primary (FAT32) drive.

I'm too lazy to google up the old posts to check what you're using on your boot
disk... so...

Question:  Does the boot disk you're using use a copy of command.com from
Windows 95 OEM Service Release 2 or on, or a copy from one of the W98 versions.
Anything earlier won't see FAT32 formatted drives.

"TC" <T...@blacklance.org> wrote in message
news:hdhl4vo393ud17l5i5q75nq2pmlo804df6@4ax.com...
> Question:  Does the boot disk you're using use a copy of command.com from
> Windows 95 OEM Service Release 2 or on, or a copy from one of the W98
versions.
> Anything earlier won't see FAT32 formatted drives.

No.  It's a DOS 6.22 boot disk.  The drive I installed Privateer to is a
500MB FAT16 partition.  The boot disk doesn't see any of the hard drive
partitions.

Rob

On Sat, 15 Feb 2003 00:08:57 +1000, in alt.games.wing-commander "blah"
<bl...@blah.com> wrote:

>"TC" <T...@blacklance.org> wrote in message
>news:hdhl4vo393ud17l5i5q75nq2pmlo804df6@4ax.com...
>> Question:  Does the boot disk you're using use a copy of command.com from
>> Windows 95 OEM Service Release 2 or on, or a copy from one of the W98
>versions.
>> Anything earlier won't see FAT32 formatted drives.
>
>No.  It's a DOS 6.22 boot disk.  The drive I installed Privateer to is a
>500MB FAT16 partition.  The boot disk doesn't see any of the hard drive
>partitions.
>

Hm...  well then, that is rather odd, isn't it...

"TC" <T...@blacklance.org> wrote in message
news:ujvq4vsmbqku7rodvqbd1lc6jl2138gk2u@4ax.com...
> >No.  It's a DOS 6.22 boot disk.  The drive I installed Privateer to is a
> >500MB FAT16 partition.  The boot disk doesn't see any of the hard drive
> >partitions.
> Hm...  well then, that is rather odd, isn't it...

Possibly DOS will only see it if the FIRST partition is FAT16.
Unfortunately I threw out the set of DOS 6.22 install disks I had.

Rob

On Sat, 15 Feb 2003 16:14:40 +1000, in alt.games.wing-commander "blah"
<bl...@blah.com> wrote:

>"TC" <T...@blacklance.org> wrote in message
>news:ujvq4vsmbqku7rodvqbd1lc6jl2138gk2u@4ax.com...
>> >No.  It's a DOS 6.22 boot disk.  The drive I installed Privateer to is a
>> >500MB FAT16 partition.  The boot disk doesn't see any of the hard drive
>> >partitions.
>> Hm...  well then, that is rather odd, isn't it...
>
>Possibly DOS will only see it if the FIRST partition is FAT16.
>Unfortunately I threw out the set of DOS 6.22 install disks I had.

More likely, the partition was set up with the W9x version of FDISK and not the
DOS 6.22 one.  After looking around a bit, it's been known to set the partition
type to values that DOS will recognize as NON-DOS partitions, yet Windows will
work with quite happily.  To check if this is the case, one just needs to take a
look at the partition tables using the DOS 6.2 version of FDISK and see what it
says.

Hi, I got this weblink from an english gentleman and it had  lots of wing
commander and privateer stuff! Perhaps any help for You there?:

http://www.wcnews.com/

It's called Wing commander CIC, I think! At least I know they have a
Privateer 1 walkthrough!?

D.K.
----------------------------------------------------------------------------
-------------------------------------------
"blah" <bl...@blah.com> skrev i meddelandet
news:b1ndu6$h0n$1@gnamma.connect.com.au...
> I'm trying to get Privateer to work (again) under Win98SE.  I've made a
boot
> disk and a FAT16 drive D, and installed the game to the FAT16 drive.  The
> boot disk fails because EMM386 doesn't like the code page option
specified.
> I used the one from the help file on the CD.  Does anyone have any
> config.sys files and autoexec.bat files they've used successfully to get
> Privateer to run?
>
> Rob
>
>

"TC" <T...@blacklance.org> wrote in message
news:541s4voaih9l3490rkppcstk4tu8jggb4r@4ax.com...
> More likely, the partition was set up with the W9x version of FDISK and
not the
> DOS 6.22 one.  After looking around a bit, it's been known to set the
partition
> type to values that DOS will recognize as NON-DOS partitions, yet Windows
will
> work with quite happily.  To check if this is the case, one just needs to
take a
> look at the partition tables using the DOS 6.2 version of FDISK and see
what it
> says.

If I can find a DOS 6.x FDisk, I'll try it!

Rob