Jump to content











Photo
- - - - -

[tool] ErrorLog


  • Please log in to reply
7 replies to this topic

#1 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 23 July 2006 - 10:49 AM

In the version 47 topic I mentioned that it would good to have a button for saving errors only.

I wrote a small program "ErrorLog" that can run inside the %Tools% directory and does that work:

Processing script: Set Keyboard
FileCopy - Failed to copy [V:\BCD\cds\XPP_DE_SP2\I386\KBDUS.DLL] to: [V:\OpenBuilder_047\Archive\Tweaks\Target\i386\system32\KBDUS.DLL]
RegHiveLoad - Failed to load registry hive: [Build] from file: [V:\OpenBuilder_047\Archive\Tweaks\Target\i386\system32\config\default]
RegWrite - Failed to write REG key in root key: [HKLM] Type: [0x1] Section: [Build\Keyboard Layout\Preload] Key: [1=00000409..]
RegWrite - Failed to write REG key in root key: [HKLM] Type: [0x1] Section: [Build\Control Panel\Keyboard] Key: [InitialKeyboardIndicators=2..]
RegHiveUnLoad - Failed to unload registry hive: [Build]
RegHiveLoad - Failed to load registry hive: [Build] from file: [V:\OpenBuilder_047\Archive\Tweaks\Target\i386\system32\setupreg.hiv]
RegWrite - Failed to write REG key in root key: [HKLM] Type: [0x1] Section: [Build\ControlSet001\Control\Keyboard Layout\DosKeybCodes] Key: [00000409=us..]
RegWrite - Failed to write REG key in root key: [HKLM] Type: [0x1] Section: [Build\ControlSet001\Control\Keyboard Layouts\00000409] Key: [Layout Text=409 English (United States)..]
RegWrite - Failed to write REG key in root key: [HKLM] Type: [0x1] Section: [Build\ControlSet001\Control\Keyboard Layouts\00000409] Key: [Layout Display Name=@%SystemRoot%\\system32\\input.dll,-5000..]
RegWrite - Failed to write REG key in root key: [HKLM] Type: [0x1] Section: [Build\ControlSet001\Control\Keyboard Layouts\00000409] Key: [Layout File=KBDUS.DLL..]
RegHiveUnLoad - Failed to unload registry hive: [Build]

Processing script: Screen resolution
RegHiveLoad - Failed to load registry hive: [Build] from file: [V:\OpenBuilder_047\Archive\Tweaks\Target\i386\system32\setupreg.hiv]
RegWrite - Failed to write REG key in root key: [HKLM] Type: [0x4] Section: [Build\ControlSet001\Services\VgaSave\Device0] Key: [DefaultSettings.BitsPerPel=32..]
RegWrite - Failed to write REG key in root key: [HKLM] Type: [0x4] Section: [Build\ControlSet001\Services\VgaSave\Device0] Key: [DefaultSettings.XResolution=800..]
RegWrite - Failed to write REG key in root key: [HKLM] Type: [0x4] Section: [Build\ControlSet001\Services\VgaSave\Device0] Key: [DefaultSettings.YResolution=600..]
RegHiveUnLoad - Failed to unload registry hive: [Build]

Processing script: Replace dll files
ExtractAllFiles - Failed to extract internal files from file: [V:\OpenBuilder_047\Projects\NanoXP\Tweak\Freedos32-Resources.script] Section:[Folder] Path to extract: [V:\OpenBuilder_047\Projects\NanoXP\Tweak\Target\I386\System32]

Processing script: Set CMD.EXE as default shell
RegHiveLoad - Failed to load registry hive: [Build] from file: [V:\OpenBuilder_047\Archive\Shell\Target\i386\system32\setupreg.hiv]
RegWrite - Failed to write REG key in root key: [HKLM] Type: [0x1] Section: [Build\Setup] Key: [CmdLine=cmd.exe..]
RegHiveUnLoad - Failed to unload registry hive: [Build]

Processing script: Create ISO
Failed to retrieve the dir size from: [V:\OpenBuilder_047\Archive\ISO\Target] - dir was not found
Failed to retrieve the file size from: [V:\OpenBuilder_047\ISO\nanoxp.iso] - file was not found


The program inclusive source code can be found here.
Have fun!

Peter

#2 Nuno Brito

Nuno Brito

    Platinum Member

  • .script developer
  • 10544 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 23 July 2006 - 11:28 AM

Good work psc!! :P


What is the syntax? :P

#3 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 23 July 2006 - 02:12 PM

Good work psc!! :P
What is the syntax? :P



The program must be located anywhere below %BaseDir%, I prefer %Tools%

Then just start it w/o arguments.

As a 'quick&dirty' program it is hardcoded to search the %BaseDir% (where it finds OpenBuilder.exe), to read "log.txt" and to write "Error.txt"

Because the source code is also included, you are free to change the hardcoded behaviour.

Peter

#4 Nuno Brito

Nuno Brito

    Platinum Member

  • .script developer
  • 10544 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 23 July 2006 - 02:41 PM

Excellent!! :P

But it doesn't work for me, I'm using this path:

C:\Documentos\OpenBuilder\Tools


Do you have any ideas?

And tried also where openbuilder was located and had no luck either, I guess it's time to starting learning some Basic language skills for a change.. :P

#5 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 24 July 2006 - 01:14 PM

Try the new version here. It tells you something about what happens:
proglog.txt in the directory where errorlog.exe is installed.

Peter

#6 Nuno Brito

Nuno Brito

    Platinum Member

  • .script developer
  • 10544 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 24 July 2006 - 02:25 PM

I've just tested it and works just fine..

Searching OpenBuilder.exe in C:\Documentos\OpenBuilder\Tools: Not found
Searching OpenBuilder.exe in C:\Documentos\OpenBuilder: Found
C:\Documentos\OpenBuilder\log.txt successfully opened for read.
C:\Documentos\OpenBuilder2 successfully opened for write.
0 Errors found.


Looks very usefull as post-process log diagnotic tool, nice work!

Just one thing that I start to notice.. these diagnostinc text files are starting to get scattered all over my openbuilder folder, perhaps it would be a good idea to define a sort of %user% folder where all these things should get placed? :P

I'm not refering to multiple profiles, but it would be preferable to have one folder where people could manage all these files.. :P

#7 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 24 July 2006 - 02:49 PM

I've just tested it and works just fine..
Looks very usefull as post-process log diagnotic tool, nice work!

Just one thing that I start to notice.. these diagnostinc text files are starting to get scattered all over my openbuilder folder, perhaps it would be a good idea to define a sort of %user% folder where all these things should get placed? :P

I'm not refering to multiple profiles, but it would be preferable to have one folder where people could manage all these files.. :P


I agree. I usually use the folder 'Scratch'. Whenever I see 'Scratch' I know that I can delete all content w/o any effect to important data.

Peter

#8 Nuno Brito

Nuno Brito

    Platinum Member

  • .script developer
  • 10544 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 24 July 2006 - 03:43 PM

Scratch sounds good.. :P




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users