Well, the connection speed does´nt rely much on the processor power...
But on type of connection and bandwidth, don´t you think?

Paul, get ADLS over your phone line.

I'm sure Paul would get ADSL if it was available, but I doubt it is.

BT need a few hudred people (tops) from that particular area, to sign up (not just be interested) to ADSL. Then BT will put that exchange on a waiting list.
To be honest, that figure seems waaayyy too high, but thats what I was told when I contacted them.

Telewest (cable internet) need even more, as the cost to bring the cable from a neighbouring town, needs to be recovered. And if there aren't enough people interested, they don't bother. 🙄

Near me, there is a town that has cable on one side of the road, but not on the other side. This is happening around various estates where one side want it, but the other doesn't. But a few on that side might want it but can't. 😕 Stupid.

The UK goverment really needs to fund projects to get cable and ADSL to more UK towns and villages.
Priority needs to be dropped, instead focusing on areas they have missed or skipped.

Col.J.P. wrote:

Don´t you have cable in the UK?

Yes, two villages down the road, but not here in
Woodstock.

Back to Blood.

I'm able to get out of it now, so instead of a black screen, I can now exit back to windows with the glide server still running.

All it says is

Starting Glide Server v1.18 (c) Paul Gardiner 2001-2002
Resolution = 512x384
Refresh rate = 60Hz
Color format = ABGR
Number of color buffers = 2
Number of aux buffers = 0
GRTEXCOMBINE@28
WinClose

Out of curiosity, if you hex edit the exe file you can find

GRAADRAWLINE@8._
GRAADRAWPOINT@4._
GRAADRAWPOLYGON@12._
GRAADRAWPOLYGONVERTEXLIST@8._
GRAADRAWTRIANGLE@24._
GRALPHABLENDFUNCTION@16._
GRALPHACOMBINE@20._
GRALPHACONTROLSITRGBLIGHTING@4._
GRALPHATESTFUNCTION@4._
GRALPHATESTREFERENCEVALUE@4._
GRBUFFERCLEAR@12._
GRBUFFERNUMPENDING@0._
GRBUFFERSWAP@4._
GRCHECKFORROOM@4._
GRCHROMAKEYMODE@4._
GRCHROMAKEYVALUE@4._
GRCLIPWINDOW@16._
GRCOLORCOMBINE@20._
GRCOLORMASK@8._
GRCONSTANTCOLORVALUE4@16._
GRCONSTANTCOLORVALUE@4._
GRCULLMODE@4._
GRDEPTHBIASLEVEL@4._
GRDEPTHBUFFERFUNCTION@4._
GRDEPTHBUFFERMODE@4._
GRDEPTHMASK@4._
GRDISABLEALLEFFECTS@0._
GRDITHERMODE@4._
GRDRAWLINE@8._
GRDRAWPLANARPOLYGON@12._
GRDRAWPLANARPOLYGONVERTEXLIST@8._
GRDRAWPOINT@4._
GRDRAWPOLYGON@12._
GRDRAWPOLYGONVERTEXLIST@8._
GRDRAWTRIANGLE@12._
GRERRORSETCALLBACK@4._
GRFOGCOLORVALUE@4._
GRFOGMODE@4._
GRFOGTABLE@4._
GRGAMMACORRECTIONVALUE@4._
GRGLIDEGETSTATE@4._
GRGLIDEGETVERSION@4._
GRGLIDEINIT@0._
GRGLIDESETSTATE@4._
GRGLIDESHAMELESSPLUG@4._
GRGLIDESHUTDOWN@0._
GRHINTS@8._
GRLFBCONSTANTALPHA@4._
GRLFBCONSTANTDEPTH@4._
GRLFBLOCK@24._
GRLFBREADREGION@28._
GRLFBWRITEREGION@32._
GRLFBUNLOCK@8._
GRLFBWRITECOLORFORMAT@4._
GRLFBWRITECOLORSWIZZLE@8._
GRRENDERBUFFER@4._
GRRESETTRISTATS@0._
GRSPLASH@20._
GRSSTCONFIGPIPELINE@12._
GRSSTCONTROL@4._
GRSSTIDLE@0._
GRSSTISBUSY@0._
GRSSTORIGIN@4._
GRSSTPERFSTATS@4._
GRSSTQUERYBOARDS@4._
GRSSTQUERYHARDWARE@4._
GRSSTRESETPERFSTATS@0._
GRSSTSCREENHEIGHT@0._
GRSSTSCREENWIDTH@0._
GRSSTSELECT@4._
GRSSTSTATUS@0._
GRSSTVIDEOLINE@0._
GRSSTVIDMODE@8._
GRSSTVRETRACEON@0._
GRSSTWINCLOSE@0._
GRSSTWINOPEN@28._
GRTEXCALCMEMREQUIRED@16._
GRTEXCLAMPMODE@12._
GRTEXCOMBINE@28._
GRTEXCOMBINEFUNCTION@8._
GRTEXDETAILCONTROL@16._
GRTEXDOWNLOADMIPMAP@16._
GRTEXDOWNLOADMIPMAPLEVEL@32._
GRTEXDOWNLOADMIPMAPLEVELPARTIAL@40._
GRTEXDOWNLOADTABLE@12._
GRTEXDOWNLOADTABLEPARTIAL@20._
GRTEXFILTERMODE@12._
GRTEXLODBIASVALUE@8._
GRTEXMAXADDRESS@4._
GRTEXMINADDRESS@4._
GRTEXMIPMAPMODE@12._
GRTEXMULTIBASE@8._
GRTEXMULTIBASEADDRESS@20._
GRTEXNCCTABLE@8._
GRTEXSOURCE@16._
GRTEXTEXTUREMEMREQUIRED@8._
GRTRISTATS@8._
GU3DFGETINFO@8._
GU3DFLOAD@8._
GUAADRAWTRIANGLEWITHCLIP@12._
GUALPHASOURCE@4._
GUCOLORCOMBINEFUNCTION@4._
GUDRAWPOLYGONVERTEXLISTWITHCLIP@8._
GUDRAWTRIANGLEWITHCLIP@12._
GUENCODERLE16@16._
GUENDIANSWAPBYTES@4._
GUENDIANSWAPWORDS@4._
GUFOGGENERATEEXP2@8._
GUFOGGENERATEEXP@8._
GUFOGGENERATELINEAR@12._
GUFOGTABLEINDEXTOW@4._
GUMOVIESETNAME@4._
GUMOVIESTART@0._
GUMOVIESTOP@0._
GUMPDRAWTRIANGLE@12._
GUMPINIT@0._
GUMPTEXCOMBINEFUNCTION@4._
GUMPTEXSOURCE@8._
GUTEXALLOCATEMEMORY@60._
GUTEXCHANGEATTRIBUTES@48._
GUTEXCOMBINEFUNCTION@8._
GUTEXCREATECOLORMIPMAP@0._
GUTEXDOWNLOADMIPMAP@12._
GUTEXDOWNLOADMIPMAPLEVEL@12._
GUTEXGETCURRENTMIPMAP@4._
GUTEXGETMIPMAPINFO@4._
GUTEXMEMQUERYAVAIL@4._
GUTEXMEMRESET@0._
GUTEXSOURCE@4._
CONVERTANDDOWNLOADRLE@64

Sorry about the mess, but don't know if that means anything to Paul ?

Do remember that it is an ALPHA PATCH, guys, and there may be problems that Paul can't fix.
http://blood.lith.com/

Especially since it says "Voodoo2 not supported" makes me worry...

CraigG wrote:

Back to Blood. […]
Show full quote

Back to Blood.

I'm able to get out of it now, so instead of a black screen, I can now exit back to windows with the glide server still running.

All it says is

Starting Glide Server v1.18 (c) Paul Gardiner 2001-2002
Resolution = 512x384
Refresh rate = 60Hz
Color format = ABGR
Number of color buffers = 2
Number of aux buffers = 0
GRTEXCOMBINE@28
WinClose

It is good news to get anything at all. Least that means that
the Glide library isn't statically linked...

but 512x384? Glidos isn't going to like that! 😀

and ABGR (rather than ARGB)? Glidos isn't going to like that! 😀

If you can persuade 640x480 out of it, that might help.

Out of curiosity, if you hex edit the exe file you can find GRAADRAWLINE@8._ GRAADRAWPOINT@4._ […]
Show full quote

Out of curiosity, if you hex edit the exe file you can find

GRAADRAWLINE@8._
GRAADRAWPOINT@4._

That's usual. Some part of the Glide2x link stub. The bit that load GLide2x.ovl, and patches the entry points.

but 512x384? Glidos isn't going to like that!

I just noticed that.
In the glidedos.ini, I have it set to 640x480 fullscreen. As this is the res blood is set to in it's own cfg file.

That's usual. Some part of the Glide2x link stub. The bit that load GLide2x.ovl, and patches the entry points.

That was some hex entries I nicked from the actual 3dfx blood exe file. I don't understand much of it, but thought it may help.

CraigG wrote:

I just noticed that.
In the glidedos.ini, I have it set to 640x480 fullscreen. As this is the res blood is set to in it's own cfg file.

If you can find something in Blood's config that make is 640 x 480 then that might help. The Glidos setting doesn't matter. Glidos is quite happy to scale up, but it assumes the game is working at 640x480.

BTW, I have downloaded blood now. Where do I get the Glide patch?

goto [url]http://blood.lith.com,[/url]
select blood 3dfx patch,
Download either the plasma pak version or the blood registered version either one works the same

I'dd say get v1.11 blood to v1.20 patch it's the smallest and works the same as the rest of the patches,
or u could get the plasma pak patch which is 5 megs

You have to get a version that patches your particular version. Otherwise the patch won't work correctly, as it patches a lot of files and converts all the textures to the 3dfx version.

If you get the wrong one, then the patch may skip a few files because they are the wrong size.

Paul,
I now have a cd with a lot of 3dfx games all RAR'ed up and complete.
If you are interested, PM me and we'll sort something out. This should help you with gliDOS quite a bit. 😀

The site is wrong, they said blood one whole unit woulnt run the 3dfx patch and it ran fine on my old voodoo banshee, all u really need is that 3dfx.exe file with one whole unit because its already past v1.20 of blood

CraigG wrote:

Paul,
I now have a cd with a lot of 3dfx games all RAR'ed up and complete.
If you are interested, PM me and we'll sort something out. This should help you with gliDOS quite a bit. 😀

Ooo, you fine person, you! 😀

Hey glidos, how long do u think itll take to work around blood?
1 month?
3 months?
4 months?

Unregistered wrote:

Hey glidos, how long do u think itll take to work around blood? 1 month? 3 months? 4 months? […]
Show full quote

Hey glidos, how long do u think itll take to work around blood?
1 month?
3 months?
4 months?

You can never tell. It can be easy; it can be impossible.

CraigG wrote:

Back to Blood.

I'm able to get out of it now, so instead of a black screen, I can now exit back to windows with the glide server still running.

How? W98 I get stuck with a black screen. W2K the program just stops without an error message, and without Glidos picking up anything.

I'm using Blood one whole unit with 1.3MB patch.

The only way of getting out of the black screen is to use CTRL+ALT+DEL, then press escape, and keep pressing escape, ALT+F4, ALT+TAB.

You do eventually get out, but you got to keep pressing those keys.

Doesnt that gldvesa.exe thing have something to do with it bacause it's for windows xp

Try running blood with glidos vesa support its just as slow on wXP as on w98 so it doesnt have much difference,
If that doesnt work well atleast I suggested something