Hello, could you post the descripion of your problem to this thread in the Bug reports section? Add also more information about yout computer, graphics card, windows version, graphics driver version...

The behaviour, that I described, doesn't appear in W41. Maybe I could do a "regression test" for test patches between W41 and X.

In patch X, the LapsDone field is at position 76, you can check it by compiling and running the following C code:

EDIT: I changed the typedefs according to Scawen's post, to prevent confusion for readers. I use correct typedefs in my other programs, though .

Last edited by Kada_CZ, Mon, 11 Jun 2007 22:50.

How to reproduce the bug:
- run LFS, starting in fullscreen.
- click on "Hot lapping", choose Westhil rev and FZR (I think it doesn't matter what car/track you choose).
- click "Ready"
- when on track, press shift-f4 to go to windowed mode.
- click on (pop up) any another window
- now, when another window is active (and LFS window is inactive), the force feedback disapears, I'm not sure, if it's bug or feature.
- click back to the LFS window.
- pres shift-f4
- now I have black-full-screen, I can not do anything, alt-tab, ctrl-alt-del, etc..., the only way out is hardware reset.

This bug does not appear in patch W41.

LFS version -- patch X, Windows 98SE, directx 9, Nvidia GF4Ti 4200, ForceWare 81.98 (the latest for my old card).

Yes, I'm expecting "buy a new computer" reply .

Ok, If you are able to write some 4-bytes value to that address in Artmoney, then it should be correct.

What about to change "ByVal lpBuffer As Double" to "ByRef lpBuffer As Double" in the WriteProcessMemory declaration?

I would bet that you write something to the wrong location in the memory.

EDIT: I was wrong, the 57D380 is the address, am I right? Then I would check, that the value is correct and doesn't point somewhere, e.g. to the stack.

Last edited by Kada_CZ, Thu, 7 Jun 2007 19:30.

Hello
I can't find any detailed information about this:

Quote from Scawen :

Added handicap mass and restriction to hotlap file header

I found, that the mass is probably in byte #29, is that right?

It would be ideal (I know, wrong thread for improvements) if there would be information about handicaps also on the LFSWorld (e.g. in Pubstats script). The reason, why I need it, is that we use HotLaps to divide racers into divisions in our Czech LFS League. And for example we have a rule, that a setup for FZR in HotLap has to have 80Kg handicap mass. So the information about handicaps through Pubstats script would allow us to check these hotlaps without downloading the SPR. Or is there any other solution?

Last edited by Kada_CZ, Mon, 4 Jun 2007 23:00.

When I leave ("rejoin test", after 9, 8, ...., 1), I got four "Can't remove - Unknown!" messages.

Quote from Nick A :

I had a pm asking how to add a shift light, pit limiter etc...

.

Nice pdf Nick.

Quote from -Willi- :

- no one can see other ppl driving, only my own marker on map is moving, all others are standing still.

Yes, I saw this several times on ALeRT (Actual Linux, see above) servers. But the problem disapeared, I'm not sure when and why . Maybe 0.9.22 X 0.9.20?

I think that Nick_A has rev-diodes on LPT pins 9, 1, 14, 16, 17. The data pins 2-8 are used for gear display. The rest of the trick is in his adapted version of GI software.

Last edited by Kada_CZ, Sun, 27 May 2007 23:58.

Stylish :-), good work .

Congratulations

You may start with this, needs to be programed in the programmer only once, then it could be programmed by USB. Example applications (e.g. simulation of usb mouse) are also available on that page. I build it for my experiments, it's really simple, I recommend it.

Ok, great then .
According to this, pf keeps states of closed connections for 90 seconds.

/OT, from different thread:

Quote from Victor :

(this is why i love freebsd)

Nobody´s perfect but Linux and me .

Well, it explains why only freebsd->freebsd is problematic. But back to the beginning of this thread, all the problematic mysql_connect() functions was called from one freebsd box? Notice, that our freebsd machines has also net.inet.ip.portrange.randomized: 1.

Quote from Nick A :

I would like to make your gear indicator with a built-in rev indicator, using 5 LEDs connected to the remaining pins.

Simple answer, I don't plan to do that. There are too many different posibilities, what people would like to have in GI for their specific hardware :-). On the other hand, the sources for GI are released under GPL and you can download it and add functions you want... It is not complicated, if you know C. Let us know, if you make it work.

Quote from Victor :

[net.inet.tcp.rexmit_min] that value only takes 10-folds, so 10, 20, 30, etc.

Not on our freebsd, check my sysctl net values, anyway it is not the solution.

Quote from Victor :

I now disabled PF on my home freebsd install and did 3000 connections to the redhat server (E -> A)

No problems at all!

I then did the connection test towards my freebsd server in amsterdam (with PF on) and there i got problems again.

For me, the weird thing is:

Could you try to set (on your home box "E"):
net.inet.tcp.rexmit_min: 3
if you didn't try it already... And rerun test from E to A.

Quote from Victor :

And it just boggles my mind why _all_ my 4 different freebsd boxes have the problem and yours doesn't. I hope there will be some others who can do the test still.

I tested it on 3 other freebsd boxes, no errors, but they are the same hardware and configuration.... I'll do the test on some non-pc Unixes tonight, but i'm almost sure, that there will be no errors.

Could you attach your "sysctl -a"? (I'm not sure, if there aren't some sensitive informations, there are part of the logs, at least). I could ask some freebsd guru to look at it.

I did a test from a freebsd box to the ubuntu box, the machines are on different subnets (2 hops). The result was 0 (zero) errors.....

The freebsd box:
$uname -a
FreeBSD <snip> 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE
root@<snip>:/usr/obj/usr/src/sys/<snip> i386

$pciconf -lv
...
vr0@pci0:18:0: class=0x020000 card=0x80a11043 chip=0x30651106 rev=0x74 hdr=0x00
vendor = 'VIA Technologies Inc'
device = 'VT6102 Rhine II PCI Fast Ethernet Controller'
...

I don't know how to discover the driver type, I have no experience with freebsd. The kldstat command shows:

I don't think, that the specs of the Ubuntu box are relevant here, but if you want them also, let me known.

Maybe, could you run the rest of the tests (i.e. on each machine test connection to all 5 remaining boxes)?

EDIT:
/etc/sysctl.conf in the freebsd box:

Isn't the problem some freebsd anti-dos attack feature? I just read this article.

EDIT2: I attached the result of the command: sysctl -a|grep ^net

Last edited by Kada_CZ, Wed, 16 May 2007 03:07.

Quote from Victor :

I'm currently trying to find someone who can quickly get some new nics to the pop and either install them, or just deliver them to the pop.

Maybe also buy an usb keyboard and fasten it to the server.. I think, that new nics known-working-flawlessly under freebsd are the best solution.

Last edited by Kada_CZ, Tue, 15 May 2007 14:15.

Quote from ted209 :

Am I right in saying that I need a 5V one for the lpt port?

Yes. On the other hand I recommend using ULN2803 with external power source (can be higher than 5V) to protect the LPT port (see the GI page). With ULN2803, use 7-segment LED with common anode. Without ULN2803 (7-segment with resistors soldered directly to the port), use 7-segment with common cathode.

Quote from ted209 :

I'd like a nice bright big display - can anyone recommend one to me?

The best way is to go to the nearest shop with electronic supplies and see for your self :-). The display is cheap, it should be around one-two pounds.

You probably found this already, maybe you could try the suggested "fix" before compiling kernel. Just to ensure, that the problem is in the bce driver.