Valhalla Legends Archive

You have to pass a null as the third value in SetSecurityInfo(). You are passing the same paramaters that war3 uses.

As openly available as working lists of starcraft cdkeys are, I highly doubt you will sell anything, even now.

Reinstall with x32 so that you can use Ethereal.

There is a much easier way to do this: patch game.dll with 6804000080 at address 6F00996C to 6800000000. Any hex editor will work. All this does is create a null value in the third paramater of SetSecurityInfo() which makes sure the api doesnt do anything that can block you.

Edit: My apologies. This address has been changed in 1.20B and I will update the newer address and values ASAP.

Why would your bot use more than 4 to begin with?

lol

If LCase(splt(0)) = Trigger & "own" And LCase(username) = Master Then
(i dont know wut would go here)
CleanSlateBot1.Send "/ban " & username
End If
GoTo Done
Done:
If you implemented this, your code would ban the users that issued the command to the bot. You need to ban the username that matches the string you are comparing with.

Also, don't tell people you don't want their help if you post here. This thread will not only help you but any users that visit it in the future or will prevent threads like this if people use the Search page.

good observation  

Quote from: werehamster on September 21, 2004, 02:01 AM
I realized after I posted.  I have 3 other bots that didn't go down so I never thought that BNLS server wasn't at full capacity.

Also, this is not the first time I posted this questing.  I had a problem with this in the past and I just finished re-writing the code from scrath and thought it wasn't fixed yet.

I do appologize.

You do realize that BNLS has nothing to do with your connection to battle.net after the login sequence?

Another alternative would be to draw one using the API.
Public Sub CreateButton(frm As Form, Caption As String, Left As Long, Top As Long, Height As Long, Width As Long, OnClick As Long, ByRef OldhWndProc As Long)
   Dim hWnd As Long

   hWnd = CreateWindowEx(0&, "BUTTON", Caption, WS_VISIBLE Or WS_CHILD Or WS_THICKFRAME, Left, Top, Height, Width, frm.hWnd, 0&, App.hInstance, 0&)
   If hWnd And OnClick <> 0 Then
       'Set the new WindowProc to manage the button events
       OldhWndProc = SetWindowLong(hWnd, GWL_WNDPROC, OnClick)
   End If
End Sub

Public Function MyWindowProc(ByVal hWnd As Long, ByVal uMsg As Long, ByVal wParam As Long, lParam As Long) As Long
   'OnLeftButtonUp
   If uMsg = WM_LBUTTONUP Then
       'Make a sound
       Beep
   End If
   'Call the old WindowProc for the button
   MyWindowProc = CallWindowProc(myOldhWndProc, hWnd, uMsg, wParam, lParam)
End Function

Private Sub Command1_Click()
   CreateButton Me, "Button", 5, 5, 300, 100, AddressOf Module1.MyWindowProc, myOldhWndProc
End Sub

Of course, you would have to add the declarations.

Looking for opinions about Microsofts new release. I've heard alot of good things about the beta release including:

-intellisense code snippets
-brought back Edit and Continue from vb 6
-support for signed bytes and unsigned integers
-background compilation and Auto-correct

Waiting on the download to finish now. I'll post my personal opinion after I've had time to try it out.

Yea I'm a skater ~_~

Quote from: Skywing on April 28, 2004, 04:06 PM

Quote from: synth on April 28, 2004, 03:20 PM
Do you think that any other appliance or electronic device around the area could be causing interference?

Sounds more like buggy software.  Try using the default drivers and not the custom Logitech stuff that comes with the keyboard?

Logitech has a history of providing buggy things with their mice, it wouldn't surprise me if there were problems with their keyboards as well.

That's exactly what I was thinking. There are rare instances where you actually need drivers that Windows XP doesn't provide generic drivers for. I don't think that it would have anything to do with outside interference since the error is generated in a seperate application. Try reinstalling the keyboard. The most logical explanation for the error would be corrupt device drivers. If that doesn't work then try reinstalling Office XP before you go replacing your keyboard.

Also: The volume controls for media player will not work with Logitech keyboards unless their software is installed. However, the rest of the media player controls will work. (play/pause, stop, etc.)

Not big into comic books but it sounds promising. It was released yesterday. Has anyone tried it yet?


frmMain.lwRoomUsers.ListItems.Remove (frmMain.lwRoomUsers.FindItem(User).Index)
If that doesn't help then post some code.