Jump to content











Photo
- - - - -

nativeEx_BlueCon


  • This topic is locked This topic is locked
8 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 01 January 2008 - 05:23 PM

Edited by psc:
This project is replaced by nativeEx_BSOR.
I removed the download link in this post

I used (my good old, and still used) BlueCon 2000 by O&O to create a small rescue cd which can
  • Backup / restore registry
  • Regedit (text in a filesystem like tree)
  • Remove / change local user password
  • Edit files (like old Edlin)
  • Enable / disable devices
  • Enable / disable services
  • Copy, move, delete, dir etc. as known from cmd.com
  • .....
Everything works in the 'Blue Screen'
The main app is a native code program by O&O, which is renamed to SMSS.exe and therefore in the PE started as Session Manager.

Some screenshoots:
BCCommands.gif
BCProject.gif
BCScript.gif

Currently there are some technical issues to store the project on the server. Therefore here attached:
[link removed]

Unzip it into your Projects folder.

First start Basic > Build > CheckTools to download the nativeEx core.

Peter

Edited by psc, 03 January 2008 - 06:32 PM.
New replacing project


#2 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 01 January 2008 - 06:39 PM

I am not sure I understand the utility of this (with all due respect of course) :cheers:.

I mean, O&O Bluecon is a COMMERCIAL program that ALREADY builds a Recovery CD, what is the point of making a .script to replicate what it already does? :cheers:

jaclaz

#3 pscEx

pscEx

    Platinum Member

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

Posted 01 January 2008 - 06:51 PM

I am not sure I understand the utility of this (with all due respect of course) :cheers: .

I mean, O&O Bluecon is a COMMERCIAL program that ALREADY builds a Recovery CD, what is the point of making a .script to replicate what it already does? :cheers:

jaclaz

For people in a similar situation like me:

I have the BlueCon license; and I use the prog.

The above mentioned 'SMSS.EXE' is the main file of their COMMERCIAL Recovery CD!

I could either
  • Build a rescue CD using their app
    Concerns:
    • My rather old BlueCon tries to build the rescue CD or 4 start floppies from a W2000 CD.
      With the SW I have, building the CD fails, only 4 floppies can be created.
      (I still use their 4 floppies for emergencies. Imagine the boot time!)
    • nativeEx_BlueCon uses XP / W2003 source CDs and therefore contains newer HW access possibilities.
  • Buy their latest BartPE rescue CD additionally
  • Build my own WinBuilder PE rescue CE
For me choice #3 was the best, and I thought that it can be interesting for other people, too.

Peter

#4 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 01 January 2008 - 07:56 PM

With the SW I have, building the CD fails, only 4 floppies can be created.
(I still use their 4 floppies for emergencies. Imagine the boot time!)


I see. :cheers:

I did not get that your copy of O&O was somewhat malfunctioning. :cheers:

What I would have tried in my usual "dynosaur" way would have been to simply exchange the O&O SMSS.EXE with the original one and use this:
http://www.boot-land...sole-t2254.html

Since you seem to start "getting a feeling" for booting "strange" things, this is also related:
http://www.boot-land...?...ic=3537&hl=

....just imagine what you could do if you get interested and learn how to code a NATIVE app....:cheers:

:cheers:

jaclaz

#5 pscEx

pscEx

    Platinum Member

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

Posted 01 January 2008 - 08:15 PM

What I would have tried in my usual "dynosaur" way would have been to simply exchange the O&O SMSS.EXE with the original one and use this:
http://www.boot-land...sole-t2254.html

Since you seem to start "getting a feeling" for booting "strange" things, this is also related:
http://www.boot-land...?...ic=3537&hl=

....just imagine what you could do if you get interested and learn how to code a NATIVE app.... :cheers:

Thanks, Jaclaz!
As you see, a developer sometimes only sees his own issues ond forgets to 'google' :cheers:

#1 is very interesting.

But #2 personally 'attacks' me. I remember old assembler times when with the beginning of NT4 the good old code has to be changed into 'pointers' or whatever the name was. And these pointers have been fully maintained by Billy G. Not any more in my responsibility.

Maybe I can refresh some memories and try something ...

Peter

#6 TheHive

TheHive

    Platinum Member

  • .script developer
  • 4171 posts

Posted 01 January 2008 - 09:26 PM

Just to let the people that want to get their license file:
The OOBC.Lic should be found in youre Bootable ISO media when you create the BlueCon ISO.
Im using the O&O BlueCon XXL 5.0.414.


I have a question:

------------
On the following parameters where would these folders be if im using the following physical Directory for the project

L:\WINBUILDER\WinBuilder074\Projects\nativeEx_BlueCon

Where can I create these folders. Using "L:\WINBUILDER\"
%GlobalTemplates%\BlueCon
%GlobalTemplates%\W2000
%ProjectTemplates%\FBWF

-------------


Should the Source be the Windows XP source or the BlueCon ISO that one has.
Im thinking the XP source. Since you already have the Read only BlueCon file that you need the Lic file to convert to a fully licensed one.

#7 Galapo

Galapo

    Platinum Member

  • .script developer
  • 3841 posts
  •  
    Australia

Posted 01 January 2008 - 09:54 PM

Where can I create these folders. Using "L:\WINBUILDER\"
%GlobalTemplates%\BlueCon
%GlobalTemplates%\W2000
%ProjectTemplates%\FBWF

l:\winbuilder\Workbench\Common\BlueCon
l:\winbuilder\Workbench\Common\W2000
l:\winbuilder\Workbench\[project's name]\FBWF

#8 TheHive

TheHive

    Platinum Member

  • .script developer
  • 4171 posts

Posted 01 January 2008 - 10:16 PM

Thank you!

#9 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 02 January 2008 - 08:43 AM

But #2 personally 'attacks' me.
....
Maybe I can refresh some memories and try something ...


Yep, that's the idea of a challenge....:cheers:

Seriously, the Winroot thingy is a great "proof of concept" but it is pretty much unuseful in practice, if we could have new "smss.exe"'s or new "spcmdcon.sys"'s that would be great.

:cheers:

jaclaz




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users