• WSBriana

    WSBriana

    @wsbriana

    Viewing 15 replies - 1 through 15 (of 44 total)
    Author
    Replies
    • in reply to: VBS to download web pages (Win98) #874291

      Actually, I’ve done this, but I can’t find the details at the moment. If you do an internet search, using ‘readyState’ and ‘WSH’ as keywords, you should find some good examples of reading a web page through scripting.

    • in reply to: VBS to download web pages (Win98) #874292

      Actually, I’ve done this, but I can’t find the details at the moment. If you do an internet search, using ‘readyState’ and ‘WSH’ as keywords, you should find some good examples of reading a web page through scripting.

    • in reply to: Secure Application (VB6) #873856

      Sure – here’s a piece of VB6 code I whipped together.

      Option Explicit

      ‘Declare a “Dummy” date – as bait for would-be hackers
      Dim pDummyDate As String

      Private Sub Form_Load()
      ‘Now, set our dummy date.
      pDummyDate = “01/01/2004”
      Call Check_It
      End
      End Sub

      Private Sub Check_It()
      Dim i As Integer
      Dim CkSum As Long

      ‘In this routine, we add up the character values for the string, and compare
      ‘it against the checksum from the original ’01/01/2004’.
      ‘If it has changed, we know that someone has used a hex editor to try
      ‘to change the date embedded in our code.

      For i = 1 To Len(pDummyDate)
      CkSum = CkSum + Asc(Mid(pDummyDate, i, 1))
      Next

      ‘Now, check to see if the checksums match. If they don’t, we
      ‘create a bogus error.
      If CkSum 486 Then i = i / 0
      End Sub

      ———————————————

      Of course, it’s very simple, but it would work as I mentioned. You could have other
      pieces of ‘trap’ code sprinkled throughout the code. Internet addresses, for example, could
      also be used, so that a hacker couldn’t modify a hard-coded address.

    • in reply to: Secure Application (VB6) #873857

      Sure – here’s a piece of VB6 code I whipped together.

      Option Explicit

      ‘Declare a “Dummy” date – as bait for would-be hackers
      Dim pDummyDate As String

      Private Sub Form_Load()
      ‘Now, set our dummy date.
      pDummyDate = “01/01/2004”
      Call Check_It
      End
      End Sub

      Private Sub Check_It()
      Dim i As Integer
      Dim CkSum As Long

      ‘In this routine, we add up the character values for the string, and compare
      ‘it against the checksum from the original ’01/01/2004’.
      ‘If it has changed, we know that someone has used a hex editor to try
      ‘to change the date embedded in our code.

      For i = 1 To Len(pDummyDate)
      CkSum = CkSum + Asc(Mid(pDummyDate, i, 1))
      Next

      ‘Now, check to see if the checksums match. If they don’t, we
      ‘create a bogus error.
      If CkSum 486 Then i = i / 0
      End Sub

      ———————————————

      Of course, it’s very simple, but it would work as I mentioned. You could have other
      pieces of ‘trap’ code sprinkled throughout the code. Internet addresses, for example, could
      also be used, so that a hacker couldn’t modify a hard-coded address.

    • in reply to: pstorec.exe (XP SP1a) #873725

      It’s possible to have files that don’t show up at all in Windows XP. I remember reading somewhere that it was a combination of certain file attributes – sorry, can’t cite the source.

      Try opening a DOS Prompt box, then do this:

      CD WindowsSystem32
      attrib pstorec.exe

      See if the file is actually there.

      Brian

    • in reply to: pstorec.exe (XP SP1a) #873726

      It’s possible to have files that don’t show up at all in Windows XP. I remember reading somewhere that it was a combination of certain file attributes – sorry, can’t cite the source.

      Try opening a DOS Prompt box, then do this:

      CD WindowsSystem32
      attrib pstorec.exe

      See if the file is actually there.

      Brian

    • in reply to: Beginning VBA question – Creating Forms (Access 2000) #873703

      Dave:

      Yes, it’s a simple form. I found some VBA code that will do text searching and wanted to create a small db to hold some notes. The form has one text field, one listbox and two command buttons. The first text field is the search string, the listbox will be populated by the first section of each record found. The first command button will start the search, the second one clears everything. Double-clicking a listbox entry displays the whole record.

      I’ve used Access for several years, so I’m familiar with a lot of the VBA language. I agree with you – discovery is the best teacher (in my case) and I just need a minor shove in the proper direction.

      I’ve discovered a problem that may explain why I’m being hampered. The Controls Wizard is greyed out – no way to turn it on. Any ideas?

    • in reply to: Beginning VBA question – Creating Forms (Access 2000) #873704

      Dave:

      Yes, it’s a simple form. I found some VBA code that will do text searching and wanted to create a small db to hold some notes. The form has one text field, one listbox and two command buttons. The first text field is the search string, the listbox will be populated by the first section of each record found. The first command button will start the search, the second one clears everything. Double-clicking a listbox entry displays the whole record.

      I’ve used Access for several years, so I’m familiar with a lot of the VBA language. I agree with you – discovery is the best teacher (in my case) and I just need a minor shove in the proper direction.

      I’ve discovered a problem that may explain why I’m being hampered. The Controls Wizard is greyed out – no way to turn it on. Any ideas?

    • in reply to: Hijack this not removing items #873645

      I had a rather nasty malware that neither AdAware or Spybot Search and Destroy could find. They turned out to be Browser Helper Objects. I downloaded BHODemon from Majorgeeks.com. It found the two BHO offenders and let me nullify them. I also had Spybot’s Resident Shield turned on, so it warned me when the BHO’s were trying to write themselves back into my registry with a different name (seems to be a trick they’ve learned recently). I also ran MSCONFIG to find and deactivate any other startup programs that weren’t recognizable.

      One reboot – and I’m spyware free (for now)…

    • in reply to: Hijack this not removing items #873646

      I had a rather nasty malware that neither AdAware or Spybot Search and Destroy could find. They turned out to be Browser Helper Objects. I downloaded BHODemon from Majorgeeks.com. It found the two BHO offenders and let me nullify them. I also had Spybot’s Resident Shield turned on, so it warned me when the BHO’s were trying to write themselves back into my registry with a different name (seems to be a trick they’ve learned recently). I also ran MSCONFIG to find and deactivate any other startup programs that weren’t recognizable.

      One reboot – and I’m spyware free (for now)…

    • in reply to: Secure Application (VB6) #873641

      I’ve done similar routines in some of my programs. You might want to also add a couple of ‘traps’ to your code, as well. Put a clear-text field in that has a date in it. When the program runs, have it compare the checksum of the date to see if it has been changed. If it has, pop up a warning messages, stating that the program has been tampered with – then shut down.

      If you REALLY want to be nasty, have it write a value to a data file that is a ‘tamper lock’. The file would have been created when the program was running correctly, so restoring the program from a backup won’t help. They could only get it running by wiping out the data and starting fresh, or restoring from a backup – prior to the tampering. It’s not foolproof, but you just want to prevent the casual hacker. Making things too complicated can sometimes come back to bite you – hard!

      Brian

    • in reply to: Secure Application (VB6) #873642

      I’ve done similar routines in some of my programs. You might want to also add a couple of ‘traps’ to your code, as well. Put a clear-text field in that has a date in it. When the program runs, have it compare the checksum of the date to see if it has been changed. If it has, pop up a warning messages, stating that the program has been tampered with – then shut down.

      If you REALLY want to be nasty, have it write a value to a data file that is a ‘tamper lock’. The file would have been created when the program was running correctly, so restoring the program from a backup won’t help. They could only get it running by wiping out the data and starting fresh, or restoring from a backup – prior to the tampering. It’s not foolproof, but you just want to prevent the casual hacker. Making things too complicated can sometimes come back to bite you – hard!

      Brian

    • in reply to: How to distribute a control (Access 2000 SR1) #663738

      That’s what I expected to hear. Thanks for the quick reply.

      Brian

    • The RichTextBox control can be tricky. I’ve used it, but I always have to experiment with it.

      What you are looking for is not easily done, at least, for a RichtextBox. If you are using a Listbox or Listform, then you can create a sub-menu and use the control’s ShortcutMenuBar property.

      It seems like I have seen a right-click menu for a RichTextBox – somewhere – but I can’t find it right now. Do you have to use a RichTextBox control?

      Brian

    • in reply to: Boolean values on bound form (Access 2000 SR1) #662011

      Hans:
      I wasn’t actually trying to make them ‘loose’ option buttons. I had tried the Control Wizard, but I missed the part about using -1 and 0, so I could never make it work. That was perfect! Thank you!

    Viewing 15 replies - 1 through 15 (of 44 total)