Board index » delphi » TP7.0 and Win2K/WinME

TP7.0 and Win2K/WinME

My TP7.0  program don't work in graphic mode on my new Dell Inspiron 8100
using the DOS window in  WinMe. The program is running, but there is no
output on the screen. It worked very well on my Toshiba an Win98.
Have anyone else had this problem? Is there a solution? Are there any new
bgi-files? Mine are  from 1992.
 

Re:TP7.0 and Win2K/WinME


Quote
Tore Oldervoll <tolde...@online.no> wrote:
>  My TP7.0  program don't work in graphic mode on my new Dell Inspiron 8100
>  using the DOS window in  WinMe. The program is running, but there is no
>  output on the screen. It worked very well on my Toshiba an Win98.
>  Have anyone else had this problem? Is there a solution? Are there any new
>  bgi-files? Mine are  from 1992.

At least EGAVGA.BGI in 640x480x16 mode of TP 6.0 works perfectly
in WinME - so I think the 7.0 versions should work, too.

Maybe your display or graphics card does not support this
old resolution and refresh frequency (60 Hz) any more?
At least I know DirectX problems on a Dell notebook in
320x240 doublescan - chaning the frequency worked.

What about running it in a window? Does it work then? And
in full screen?

--
#!/usr/bin/perl
no warnings;$,=('~'x80)."\r";END{print"\n"}print
                 ~_^  1004  ^_^  1818,  m }^_^{ }  *_*  KGBENTE=>5423683
,'n...@durchnull.de'

Re:TP7.0 and Win2K/WinME


Re:TP7.0 and Win2K/WinME


I have tried to run in a window and i full screen, and it's not working. My
machine use the new NVIDIA GeForce 2 go (Dell Mobile) card. Is that the
problem. I have tried to run it in 60 Hz, but my program does not work.

Could the card be the problem?

"Rudolf Polzer" <adsgoh...@durchnull.de> skrev i melding
news:slrn9pstfv.stf.adsgohere@www42.durchnull.de...

Quote
> Tore Oldervoll <tolde...@online.no> wrote:
> >  My TP7.0  program don't work in graphic mode on my new Dell Inspiron
8100
> >  using the DOS window in  WinMe. The program is running, but there is no
> >  output on the screen. It worked very well on my Toshiba an Win98.
> >  Have anyone else had this problem? Is there a solution? Are there any
new
> >  bgi-files? Mine are  from 1992.

> At least EGAVGA.BGI in 640x480x16 mode of TP 6.0 works perfectly
> in WinME - so I think the 7.0 versions should work, too.

> Maybe your display or graphics card does not support this
> old resolution and refresh frequency (60 Hz) any more?
> At least I know DirectX problems on a Dell notebook in
> 320x240 doublescan - chaning the frequency worked.

> What about running it in a window? Does it work then? And
> in full screen?

> --
> #!/usr/bin/perl
> no warnings;$,=('~'x80)."\r";END{print"\n"}print
>                  ~_^  1004  ^_^  1818,  m }^_^{ }  *_*  KGBENTE=>5423683
> ,'n...@durchnull.de'

Re:TP7.0 and Win2K/WinME


Re:TP7.0 and Win2K/WinME


Quote
Rudolf Polzer wrote:
> Tore Oldervoll <tolde...@online.no> wrote:

>> My TP7.0  program don't work in graphic mode on my new Dell Inspiron 8100
>> using the DOS window in  WinMe. The program is running, but there is no
>> output on the screen. It worked very well on my Toshiba an Win98.
>> Have anyone else had this problem? Is there a solution? Are there any new
>> bgi-files? Mine are  from 1992.

> At least EGAVGA.BGI in 640x480x16 mode of TP 6.0 works perfectly
> in WinME - so I think the 7.0 versions should work, too.

> Maybe your display or graphics card does not support this
> old resolution and refresh frequency (60 Hz) any more?
> At least I know DirectX problems on a Dell notebook in
> 320x240 doublescan - chaning the frequency worked.

> What about running it in a window? Does it work then? And
> in full screen?

Why can't the damm hardware producers keep their hands off the
compatible things? Why always invent a new Hardwaredesign in SUCH a way,
that all compatible soulutins which already exist won't work on the new
hardware??? Get they money from M$ for doing so or what??

Markus

Re:TP7.0 and Win2K/WinME


Quote
Markus Humm <markus.h...@freenet.de> wrote:
>  Rudolf Polzer wrote:
[640x480x4bit]
>  Why can't the damm hardware producers keep their hands off the
>  compatible things? Why always invent a new Hardwaredesign in SUCH a way,
>  that all compatible soulutins which already exist won't work on the new
>  hardware??? Get they money from M$ for doing so or what??

No, but if they do not follow M$, they won't be able to release
a 'certified' driver for XP. And only certified drivers work
in XP :(

--
Mailer:
  Wat mutt, dat mutt.

                                            http://rebou...@durchnull.de

Re:TP7.0 and Win2K/WinME


Quote
Jim Higgins wrote:
> On Wed, 12 Sep 2001 22:11:29 +0200, in
> <3B9FC171.5040...@freenet.de>, Markus Humm
> <markus.h...@freenet.de> wrote:

>>Rudolf Polzer wrote:

>>>Tore Oldervoll <tolde...@online.no> wrote:

>>>>My TP7.0  program don't work in graphic mode on my new Dell Inspiron 8100
>>>>using the DOS window in  WinMe. The program is running, but there is no
>>>>output on the screen. It worked very well on my Toshiba an Win98.
>>>>Have anyone else had this problem? Is there a solution? Are there any new
>>>>bgi-files? Mine are  from 1992.

>>>At least EGAVGA.BGI in 640x480x16 mode of TP 6.0 works perfectly
>>>in WinME - so I think the 7.0 versions should work, too.

>>>Maybe your display or graphics card does not support this
>>>old resolution and refresh frequency (60 Hz) any more?
>>>At least I know DirectX problems on a Dell notebook in
>>>320x240 doublescan - chaning the frequency worked.

>>>What about running it in a window? Does it work then? And
>>>in full screen?

>>Why can't the damm hardware producers keep their hands
>>off the compatible things? Why always invent a new
>>Hardwaredesign in SUCH a way, that all compatible soulutins
>>which already exist won't work on the new hardware???
>>Get they money from M$ for doing so or what??

> I share your frustration, but... everything can't remain 100%
> compatible back to the days of DOS 3.1 forever.  It's called
> progress.  Some folks like to work on Model T's or Mustangs from
> the 60s, but they don't expect to be able to buy compatible parts
> from their Ford dealer.

> Those who need old hardware to run a favorite program can
> probably find it on eBAY - at exorbitant prices.

But I for my old Volkswagen Beetle (if I had one) could JUST DO THIS! If
the dealer couldn't provide me with these spare parts, I only had to
contact Wolfsburg (the city, Volkswagens headquarter and biggest
production plant is). They even would (okay it would cost more) rebuild
parts not at warehouse from the old construction plans!

And new hardware has not always the need to thorow away old compatible
interfaces. Why always reinvent the wheel by reprogramming the existing
software (that would be okay for it's purpose) only because the hardware
changed a little bit? This is redundand work!!! If the hardware builders
had to pay every programmer for the need of doing such work, they would
build in the compatible APIs, because that would be cheaper for them...

Markus

Other Threads