A Windows 98 & ME forum. Win98banter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » Win98banter forum » Windows 98 » General
Site Map Home Authors List Search Today's Posts Mark Forums Read Web Partners

Ensoniq Creative AudioPCI sound card autoexec.bat woes



 
 
Thread Tools Display Modes
  #1  
Old June 22nd 08, 12:31 PM posted to microsoft.public.win98.gen_discussion
rpgs rock dvds
External Usenet User
 
Posts: 89
Default Ensoniq Creative AudioPCI sound card autoexec.bat woes

The driver package for this card installs an unwanted legacy audio
device inside Device Manager. It also adds a "SET BLASTER" line
inside autoexec.bat, which "cancels out" my own SET BLASTER line for
my real SoundBlaster card.

If I remove the unwanted SET BLASTER line, the legacy audio device
simply adds it back in after a reboot.

If I remove the legacy audio device from Device Manager (by removing
it from my specific hardware configuration profile), what happens is
that after any reboot, I find that my own specific SET BLASTER line
gets removed!

Now that the legacy audio device has been removed from my specific
hardware configuration profile, how can I stop it continuing to meddle
with my autoexec.bat file?

Any thoughts gratefully received. Thank you. Best regards, Robert.
  #2  
Old June 22nd 08, 05:51 PM posted to microsoft.public.win98.gen_discussion
Gary S. Terhune[_2_]
External Usenet User
 
Posts: 2,158
Default Ensoniq Creative AudioPCI sound card autoexec.bat woes

"rpgs rock dvds" wrote in message
...
The driver package for this card installs an unwanted legacy audio
device inside Device Manager. It also adds a "SET BLASTER" line
inside autoexec.bat, which "cancels out" my own SET BLASTER line for
my real SoundBlaster card.


What do you mean your "real Soundblaster card"? If you 've already got your
"real" card in there, why are you installing another driver package for it?
Or do you have TWO Soundblaster cards? What's the difference between the two
Autoexec.bat lines. How does each one read? I peresume they're different?

If I remove the unwanted SET BLASTER line, the legacy audio device
simply adds it back in after a reboot.


Yes, it would do that. Why would you need the SET BLASTER line in
Autoexec.bat if you arne't loading any DOS drivers for the card?

If I remove the legacy audio device from Device Manager (by removing
it from my specific hardware configuration profile), what happens is
that after any reboot, I find that my own specific SET BLASTER line
gets removed!


I would expect that, also.

Now that the legacy audio device has been removed from my specific
hardware configuration profile, how can I stop it continuing to meddle
with my autoexec.bat file?


If the legacy SB device is removed, there shouldn't be any need for any
commands relating to it to be found ANYWHERE, including not in Autoexec.bat.
Why would you think otherwise?

Any thoughts gratefully received. Thank you. Best regards, Robert.


Answers to questioned that have been asked would be greatly appreciciated.
You either have a wrong idea about that line (and any others) in
Autoexec.bat or you really are trying to install two SB cards. You got me
curious as all get out. Are you really installing two sound cards?

--
Gary S. Terhune
MS-MVP Shell/User
http://grystmill.com



  #3  
Old June 22nd 08, 06:05 PM posted to microsoft.public.win98.gen_discussion
Don Phillipson[_5_]
External Usenet User
 
Posts: 440
Default Ensoniq Creative AudioPCI sound card autoexec.bat woes

"rpgs rock dvds" wrote in message
...

The driver package for this card installs an unwanted legacy audio
device inside Device Manager. It also adds a "SET BLASTER" line
inside autoexec.bat, which "cancels out" my own SET BLASTER line for
my real SoundBlaster card.

If I remove the unwanted SET BLASTER line, the legacy audio device
simply adds it back in after a reboot.


This is normal for DOS apps (e.g. legacy software for Win95/98).

The question is why you need to load any DOS apps. or drivers
(perhaps for a DOS game: if so, you could do this via AUTOEXEC.DOS
for this particular game, activated uniquely for it via its own
/ Properties / Program / Advanced
where you check the two boxes
MS-DOS mode
and
Specify a new MS-DOS configuration
and write the commands into the two boxes for CONFIG.SYS
and AUTOEXEC.BAT.

But at least some of these games run perfectly well under
Windows, i.e. use Windows drivers, and need no CONFIG.SYS
and AUTOEXEC.BAT at boot -- only those specific to a single
DOS app as above.

--
Don Phillipson
Carlsbad Springs
(Ottawa, Canada)


  #4  
Old June 22nd 08, 06:29 PM posted to microsoft.public.win98.gen_discussion
rpgs rock dvds
External Usenet User
 
Posts: 89
Default Ensoniq Creative AudioPCI sound card autoexec.bat woes

On 22 Jun, 17:51, "Gary S. Terhune" none wrote:
"rpgs rock dvds" wrote in ...

The driver package for this card installs an unwanted legacy audio
device inside Device Manager. *It also adds a "SET BLASTER" line
inside autoexec.bat, which "cancels out" my own SET BLASTER line for
my real SoundBlaster card.


What do you mean your "real Soundblaster card"? If you 've already got your
"real" card in there, why are you installing another driver package for it?
Or do you have TWO Soundblaster cards? What's the difference between the two
Autoexec.bat lines. How does each one read? I peresume they're different?

If I remove the unwanted SET BLASTER line, the legacy audio device
simply adds it back in after a reboot.


Yes, it would do that. Why would you need the SET BLASTER line in
Autoexec.bat if you arne't loading any DOS drivers for the card?

If I remove the legacy audio device from Device Manager (by removing
it from my specific hardware configuration profile), what happens is
that after any reboot, I find that my own specific SET BLASTER line
gets removed!


I would expect that, also.

Now that the legacy audio device has been removed from my specific
hardware configuration profile, how can I stop it continuing to meddle
with my autoexec.bat file?


If the legacy SB device is removed, there shouldn't be any need for any
commands relating to it to be found ANYWHERE, including not in Autoexec.bat.
Why would you think otherwise?

Any thoughts gratefully received. *Thank you. *Best regards, Robert..


Answers to questioned that have been asked would be greatly appreciciated..
You either have a wrong idea about that line (and any others) in
Autoexec.bat or you really are trying to install two SB cards. You got me
curious as all get out. Are you really installing two sound cards?

--
Gary S. Terhune
MS-MVP Shell/Userhttp://grystmill.com


I will rephrase my OP in order to answer your queries -

My PC has the following two physical sound cards in it -

1) An ISA-based (non Plug and Play) AWE32 card.
2) A PCI-based Ensoniq PCIAudio ES1371 (which uses Creative drivers).

I installed the AWE32 first, for DOS usage. (I decided at this stage
not to ask Win98SE to search for any new hardware.)

Secondly, I inserted the ES card, and the Windows98 Creative driver
package was then duly installed. This driver package not only
installed the Windows driver for the ES card, but it also installed
another device which was called a "legacy audio device" for old DOS
games. I then asked Windows98 to add new hardware, in order to add in
the AWE32 card. It did this fine without any problems.

The problem is this: I really don't need the ES legacy audio device,
because what this legacy device does is add in its own SET BLASTER
line to the autoexec.bat file, which is as follows -

SET BLASTER A220 I5 D1 T4

This "overrides" my specific AWE32 SET BLASTER line, which is -

SET BLASTER A220 I7 D1 H5 P300 E620 T6

If I remove the ES legacy SET BLASTER line, after a reboot, this line
just gets added back in to the autoexec.bat file. If I either remove
or disable the legacy audio device, it not only removes its own SET
BLASTER line (which it should do), but crucially it unintelligently
also removes *my own* SET BLASTER line which I want to use for my
"real soundblaster", ie my AWE32 card.

To summarise: after either removing or disabling the unwanted ES
legacy audio device, I am finding that my own specific SET BLASTER
line which I want for my AWE32 card is *always* being removed from the
autoexec.bat file. It is like the legacy audio device is still
meddling with my autoexec.bat file, even though I have tried either
disabling it or I have also removed it from my current specific
hardware configuration profile. (In other words I've tried both
approaches - either disabling the legacy device, and I've also tried
removing it --- in both cases, Device Manager tells me that they are
either disabled or gone from my current hardware profile.)
  #5  
Old June 22nd 08, 06:35 PM posted to microsoft.public.win98.gen_discussion
rpgs rock dvds
External Usenet User
 
Posts: 89
Default Ensoniq Creative AudioPCI sound card autoexec.bat woes

On 22 Jun, 18:05, "Don Phillipson" wrote:
"rpgs rock dvds" wrote in ...

The driver package for this card installs an unwanted legacy audio
device inside Device Manager. *It also adds a "SET BLASTER" line
inside autoexec.bat, which "cancels out" my own SET BLASTER line for
my real SoundBlaster card.


If I remove the unwanted SET BLASTER line, the legacy audio device
simply adds it back in after a reboot.


This is normal for DOS apps (e.g. legacy software for Win95/98).

The question is why you need to load any DOS apps. or drivers
(perhaps for a DOS game: *if so, *you could do this via AUTOEXEC.DOS
for this particular game, activated uniquely for it via its own
/ Properties / Program / Advanced
where you check the two boxes
MS-DOS mode
and
Specify a new MS-DOS configuration
and write the commands into the two boxes for CONFIG.SYS
and AUTOEXEC.BAT.

But at least some of these games run perfectly well under
Windows, i.e. use Windows drivers, and need no CONFIG.SYS
and AUTOEXEC.BAT at boot -- only those specific to a single
DOS app as above.

--
Don Phillipson
Carlsbad Springs
(Ottawa, Canada)


I really want to be able to restart Win98 in "pure DOS mode" for some
DOS apps. And please note that I already do what you say in your post
re running DOS apps.

Unfortunately, I am finding that the (disabled or removed) Ensoniq
legacy audio device is still meddling with the autoexec.bat file which
I have carefully "fine-tuned" for my specific DOS requirements, which
I set-up in the manner you described in your post.
  #6  
Old June 22nd 08, 06:43 PM posted to microsoft.public.win98.gen_discussion
Gary S. Terhune[_2_]
External Usenet User
 
Posts: 2,158
Default Ensoniq Creative AudioPCI sound card autoexec.bat woes

Why do you need two audio cards if both of then support DOS? Why not get rid
of the ISA card altogether? Or is that the only one that has the game
controllers ports that you need?

I think Don has your answer.

--
Gary S. Terhune
MS-MVP Shell/User
http://grystmill.com

"rpgs rock dvds" wrote in message
...
On 22 Jun, 17:51, "Gary S. Terhune" none wrote:
"rpgs rock dvds" wrote in
...

The driver package for this card installs an unwanted legacy audio
device inside Device Manager. It also adds a "SET BLASTER" line
inside autoexec.bat, which "cancels out" my own SET BLASTER line for
my real SoundBlaster card.


What do you mean your "real Soundblaster card"? If you 've already got
your
"real" card in there, why are you installing another driver package for
it?
Or do you have TWO Soundblaster cards? What's the difference between the
two
Autoexec.bat lines. How does each one read? I peresume they're different?

If I remove the unwanted SET BLASTER line, the legacy audio device
simply adds it back in after a reboot.


Yes, it would do that. Why would you need the SET BLASTER line in
Autoexec.bat if you arne't loading any DOS drivers for the card?

If I remove the legacy audio device from Device Manager (by removing
it from my specific hardware configuration profile), what happens is
that after any reboot, I find that my own specific SET BLASTER line
gets removed!


I would expect that, also.

Now that the legacy audio device has been removed from my specific
hardware configuration profile, how can I stop it continuing to meddle
with my autoexec.bat file?


If the legacy SB device is removed, there shouldn't be any need for any
commands relating to it to be found ANYWHERE, including not in
Autoexec.bat.
Why would you think otherwise?

Any thoughts gratefully received. Thank you. Best regards, Robert.


Answers to questioned that have been asked would be greatly appreciciated.
You either have a wrong idea about that line (and any others) in
Autoexec.bat or you really are trying to install two SB cards. You got me
curious as all get out. Are you really installing two sound cards?

--
Gary S. Terhune
MS-MVP Shell/Userhttp://grystmill.com


I will rephrase my OP in order to answer your queries -

My PC has the following two physical sound cards in it -

1) An ISA-based (non Plug and Play) AWE32 card.
2) A PCI-based Ensoniq PCIAudio ES1371 (which uses Creative drivers).

I installed the AWE32 first, for DOS usage. (I decided at this stage
not to ask Win98SE to search for any new hardware.)

Secondly, I inserted the ES card, and the Windows98 Creative driver
package was then duly installed. This driver package not only
installed the Windows driver for the ES card, but it also installed
another device which was called a "legacy audio device" for old DOS
games. I then asked Windows98 to add new hardware, in order to add in
the AWE32 card. It did this fine without any problems.

The problem is this: I really don't need the ES legacy audio device,
because what this legacy device does is add in its own SET BLASTER
line to the autoexec.bat file, which is as follows -

SET BLASTER A220 I5 D1 T4

This "overrides" my specific AWE32 SET BLASTER line, which is -

SET BLASTER A220 I7 D1 H5 P300 E620 T6

If I remove the ES legacy SET BLASTER line, after a reboot, this line
just gets added back in to the autoexec.bat file. If I either remove
or disable the legacy audio device, it not only removes its own SET
BLASTER line (which it should do), but crucially it unintelligently
also removes *my own* SET BLASTER line which I want to use for my
"real soundblaster", ie my AWE32 card.

To summarise: after either removing or disabling the unwanted ES
legacy audio device, I am finding that my own specific SET BLASTER
line which I want for my AWE32 card is *always* being removed from the
autoexec.bat file. It is like the legacy audio device is still
meddling with my autoexec.bat file, even though I have tried either
disabling it or I have also removed it from my current specific
hardware configuration profile. (In other words I've tried both
approaches - either disabling the legacy device, and I've also tried
removing it --- in both cases, Device Manager tells me that they are
either disabled or gone from my current hardware profile.)


  #7  
Old June 22nd 08, 06:50 PM posted to microsoft.public.win98.gen_discussion
MEB[_2_]
External Usenet User
 
Posts: 1,626
Default Ensoniq Creative AudioPCI sound card autoexec.bat woes



"rpgs rock dvds" wrote in message
...
| The driver package for this card installs an unwanted legacy audio
| device inside Device Manager. It also adds a "SET BLASTER" line
| inside autoexec.bat, which "cancels out" my own SET BLASTER line for
| my real SoundBlaster card.
|
| If I remove the unwanted SET BLASTER line, the legacy audio device
| simply adds it back in after a reboot.
|
| If I remove the legacy audio device from Device Manager (by removing
| it from my specific hardware configuration profile), what happens is
| that after any reboot, I find that my own specific SET BLASTER line
| gets removed!
|
| Now that the legacy audio device has been removed from my specific
| hardware configuration profile, how can I stop it continuing to meddle
| with my autoexec.bat file?
|
| Any thoughts gratefully received. Thank you. Best regards, Robert.

There are generally a few things that can be done.

One is to check the installation INFs prior to driver installation, to see
if you can remove the specific settings for the DOS emulation entries, and
by doing so, defeat their installation. This will generally work in most
instances and provides the most stable setups *WHEN POSSIBLE*.
Errors can occur when the device actually needs the emulation/DOS
autoexec.bat entry to initialize its full complement of ISA/PCI/PnP aspects
[generally found in older/early ISA and ISA PnP cards or *cheapo/knockoff*
PCI cards]. This then copies those modified INFs to the INF directory
during installation, defeating errors in later installations of devices
[when you see that "building device information data base"]. This CAN,
however, cause unseen conflicts and/or errors IF the device IS PnP [chip
code discovery] and attempts to constantly set its requirements, even when
disabled or not installed. There MAY be debug routines and/or chip writing
apps which can make these modifications [semi]permanent, if supported on the
device.
See this group for a recent discussion:
EMM386: Unrecoverable privileged operation error #I7 - 05/26/2008 -
05/29/2008

Another is to allow the installation, but disable [not remove] DOS SB
support in Device Manager for the secondary device. IF the second card has
removed the primary card's DOS support, then run Device Manager Install
New Hardware and see if it will re-find the original DOS emulation for the
primary card.

Another is to install the secondary card FIRST, disable DOS SB emulation
support, shut down, restart, check autoexec and remove the old line(s) then
install the actual primary card and driver. Check the autoexec.bat for
improper entries. It may take more than one restart to get everything right.

If you're attempting this AFTER installations, then open the installation
INFs [located in %windir%\INF\] and find the registry entries that were
created, then manually modify or remove the relevant entries from the
registry [export them first in case you make a mistake or they aren't the
right entries]. Also check in win.ini and system.ini to see if they contain
entries which need removed. This requires you be familiar with the registry,
its editing and areas, Windows directory installation entries [digit codes
at times], and other aspects that many may not be familiar with.

--
MEB
http://peoplescounsel.orgfree.com
--
_________



  #8  
Old June 22nd 08, 07:00 PM posted to microsoft.public.win98.gen_discussion
rpgs rock dvds
External Usenet User
 
Posts: 89
Default Ensoniq Creative AudioPCI sound card autoexec.bat woes

On 22 Jun, 18:43, "Gary S. Terhune" none wrote:
Why do you need two audio cards if both of then support DOS? Why not get rid
of the ISA card altogether? Or is that the only one that has the game
controllers ports that you need?

I think Don has your answer.


1) I really want both sound cards: The ISA-based AWE32 card gives me
DOS MIDI daughter board based music, and the PCI Ensoniq gives me good
Windows based MIDI music using large file patch sets.

2) re Don answer, I'm afraid I am already using this approach to exit
to DOS, and I am finding that the autoexec.bat file still gets
tampered with.
  #9  
Old June 22nd 08, 07:17 PM posted to microsoft.public.win98.gen_discussion
MEB[_2_]
External Usenet User
 
Posts: 1,626
Default Ensoniq Creative AudioPCI sound card autoexec.bat woes


"MEB" meb@not wrote in message
...
|
|
| "rpgs rock dvds" wrote in message
| ...
| | The driver package for this card installs an unwanted legacy audio
| | device inside Device Manager. It also adds a "SET BLASTER" line
| | inside autoexec.bat, which "cancels out" my own SET BLASTER line for
| | my real SoundBlaster card.
| |
| | If I remove the unwanted SET BLASTER line, the legacy audio device
| | simply adds it back in after a reboot.
| |
| | If I remove the legacy audio device from Device Manager (by removing
| | it from my specific hardware configuration profile), what happens is
| | that after any reboot, I find that my own specific SET BLASTER line
| | gets removed!
| |
| | Now that the legacy audio device has been removed from my specific
| | hardware configuration profile, how can I stop it continuing to meddle
| | with my autoexec.bat file?
| |
| | Any thoughts gratefully received. Thank you. Best regards, Robert.
|
| There are generally a few things that can be done.
|
| One is to check the installation INFs prior to driver installation, to
see
| if you can remove the specific settings for the DOS emulation entries, and
| by doing so, defeat their installation. This will generally work in most
| instances and provides the most stable setups *WHEN POSSIBLE*.
| Errors can occur when the device actually needs the emulation/DOS
| autoexec.bat entry to initialize its full complement of ISA/PCI/PnP
aspects
| [generally found in older/early ISA and ISA PnP cards or *cheapo/knockoff*
| PCI cards]. This then copies those modified INFs to the INF directory
| during installation, defeating errors in later installations of devices
| [when you see that "building device information data base"]. This CAN,
| however, cause unseen conflicts and/or errors IF the device IS PnP [chip
| code discovery] and attempts to constantly set its requirements, even when
| disabled or not installed. There MAY be debug routines and/or chip writing
| apps which can make these modifications [semi]permanent, if supported on
the
| device.
| See this group for a recent discussion:
| EMM386: Unrecoverable privileged operation error #I7 - 05/26/2008 -
| 05/29/2008
|
| Another is to allow the installation, but disable [not remove] DOS SB
| support in Device Manager for the secondary device. IF the second card has
| removed the primary card's DOS support, then run Device Manager Install
| New Hardware and see if it will re-find the original DOS emulation for the
| primary card.
|
| Another is to install the secondary card FIRST, disable DOS SB emulation
| support, shut down, restart, check autoexec and remove the old line(s)
then
| install the actual primary card and driver. Check the autoexec.bat for
| improper entries. It may take more than one restart to get everything
right.
|
| If you're attempting this AFTER installations, then open the installation
| INFs [located in %windir%\INF\] and find the registry entries that were
| created, then manually modify or remove the relevant entries from the
| registry [export them first in case you make a mistake or they aren't the
| right entries]. Also check in win.ini and system.ini to see if they
contain
| entries which need removed. This requires you be familiar with the
registry,
| its editing and areas, Windows directory installation entries [digit codes
| at times], and other aspects that many may not be familiar with.
|
| --
| MEB

I should add, that when dealing with multifunction devices, or devices
which use this entry in Device Manager, it becomes somewhat more difficult
to remove its settings. Such as: modem sound card combos; modem sound
card IDE or proprietary CDROM interface other ....

--
MEB
http://peoplescounsel.orgfree.com
--
_________



  #10  
Old June 22nd 08, 07:28 PM posted to microsoft.public.win98.gen_discussion
rpgs rock dvds
External Usenet User
 
Posts: 89
Default Ensoniq Creative AudioPCI sound card autoexec.bat woes

On 22 Jun, 18:50, "MEB" meb@not wrote:

my OP snipped to prevent this post getting too large and unwieldy

*There are generally a few things that can be done.

*One is to check the installation INFs prior to driver installation, to see
if you can remove the specific settings for the DOS emulation entries, and
by doing so, defeat their installation. This will generally work in most
instances and provides the most stable setups *WHEN POSSIBLE*.
*Errors can occur when the device actually needs the emulation/DOS
autoexec.bat entry to initialize its full complement of ISA/PCI/PnP aspects
[generally found in older/early ISA and ISA PnP cards or *cheapo/knockoff*
PCI cards]. *This then copies those modified INFs to the INF directory
during installation, defeating errors in later installations of devices
[when you see that "building device information data base"]. This CAN,
however, cause unseen conflicts and/or errors IF the device IS PnP [chip
code discovery] and attempts to constantly set its requirements, even when
disabled or not installed. There MAY be debug routines and/or chip writing
apps which can make these modifications [semi]permanent, if supported on the
device.
See this group for a recent discussion:
EMM386: Unrecoverable privileged operation error #I7 - 05/26/2008 -
05/29/2008

*Another is to allow the installation, but disable [not remove] DOS SB
support in Device Manager for the secondary device. IF the second card has
removed the primary card's DOS support, then run Device Manager Install
New Hardware and see if it will re-find the original DOS emulation for the
primary card.

*Another is to install the secondary card FIRST, disable DOS SB emulation
support, shut down, restart, check autoexec and remove the old line(s) then
install the actual primary card and driver. Check the autoexec.bat *for
improper entries. It may take more than one restart to get everything right.

*If you're attempting this AFTER installations, then open the installation
INFs [located in %windir%\INF\] and find the registry entries that were
created, then manually modify or remove the relevant entries from the
registry [export them first in case you make a mistake or they aren't the
right entries]. Also check in win.ini and system.ini to see if they contain
entries which need removed. This requires you be familiar with the registry,
its editing and areas, Windows directory installation entries [digit codes
at times], and other aspects that many may not be familiar with.

--
*MEB
*http://peoplescounsel.orgfree.com
--
_________


This looks very interesting - I want to look in to this but right now
I'm quite tired because I've been on the machine for over 10 hours and
I need to stop for a rest. Incidentally I did manage a "quick fix" by
adding this line to the autoexec.bat file -

call mybat.bat
(rest of autoexec.bat lines here...)

Inside the file called mybat.bat, I have my SET BLASTER line.

By doing this, the "Creative/Ensoniq meddling" doesn't affect what is
inside the mybat.bat file.

However I really want to get this fixed properly, so when I've rested
I am going to explore INF files, etc. (Never done that before!)

Thanks!
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Sound woes Martin General 2 June 26th 05 05:50 PM
Sound Woes.... Mike Multimedia 2 November 4th 04 07:39 PM
Sound Blaster AudioPCI 128D Ashley Setup & Installation 2 September 22nd 04 02:02 PM
No sound, Creative Labs, WinME (ATTN: Mart & Noel Paton) Doug Hardware 3 July 8th 04 04:54 PM
CREATIVE SOUND BLASTER LIVE 5.1 SOUND CARDS KITTY Multimedia 0 June 12th 04 05:38 PM


All times are GMT +1. The time now is 04:09 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 Win98banter.
The comments are property of their posters.