Xref: news-dnh.mv.net comp.os.ms-windows.programmer.misc:31992 comp.os.msdos.djgpp:3457
Newsgroups: comp.os.msdos.djgpp,comp.os.ms-windows.programmer.misc
Path: news-dnh.mv.net!mv!news.NH.Destek.Net!news2.net99.net!agis!usenet.eel.ufl.edu!newsfeed.internetmci.com!in2.uu.net!EU.net!sun4nl!phcoms4.seri.philips.nl!newssvr!kunst
From: kunst AT natlab DOT research DOT philips DOT com (Pieter Kunst)
Subject: Re: RSXWDK/Windows question
Sender: news AT natlab DOT research DOT philips DOT com (USENET News System)
Organization: Philips Research Laboratories, Eindhoven, The Netherlands
References: <48tk7s$qpk AT snocap DOT cs DOT umd DOT edu>
Date: Wed, 22 Nov 1995 12:00:14 GMT
Lines: 14
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway: from newsgroup comp.os.msdos.djgpp

In article <48tk7s$qpk AT snocap DOT cs DOT umd DOT edu> dfs AT cs DOT umd DOT edu (Daniel F. Savarese) writes:
>
>To test the frame buffer I was writing a picture in a memory buffer into the
>bitmap using SetBitmapBits(hbmp, width*height, buff) and writing the bitmap
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
If this function is expecting a 16-bit int for the size, you'll indeed
get problems with bitmaps greater than 256x256.
If it expects a 32-bit int, maybe width*1L*height helps.

Just my 2 cents.

Pieter

PS I don't use RSX.