86 replies to this topic

[smiley]

Alexei is right. We should keep a "safety distance" from the border line. And Phox's images are also good.

[TheHive]

This is my suggestion for WinBuilder Boot Image.
It is already recognizable from the Forum and Splash screen.

Ill see what I can do. In my original idea I did not want to include any text in the image that would mention the forum name, Nuno, or my name within the boot screen. Mainly because I believe in the user having a clean looking bootscreen. But I will see if I can minipulate it a bit more.

[Brito]

This would also make the boot screen more "universal", any project would be able to use it..

[TheHive]

Here is one that I have been working on for a while. Trying to clean it up using only the 16 color limit but trying to maintain a translucency to the CD. The display it suppose to stand out because its what the project is about. Its the main focus when I started to clean it up.

Original before clean up


After getting down and cleaning it up.


Suggested from phox









BMP's of the above:
 BootImages.zip   262.4KB   366 downloads

[was_jaclaz]

My two cents, OK, three:
1) I would keep the "Boot Land" logo, without the "trailing" USB and CD, making it a little smaller and adding under it, in small characters "our" address www.boot-land.net
2) The monitor looks too "flat", expecially the stand of it, I would try to make a perspective image, something like this:

(you know how much I suck at graphics )

3) I would keep the WinBuilder reference inside the monitor, and let go the Copyright , let the lamers have the image if they want it.

jaclaz

[Alexei]

Maybe we should remove 640x480x16 limitation?
I did some preliminary research. It looks like "vgapnp.sys" should support VESA sompatible SVGA, i.e. at least 800x600x256 Also I found that txtsetup.sif has [Map.Display] and [Display.Load] sections that define "initial"graphic driver.
So far, I still don't know how to specify resolution and color depth

Alexei

[TheHive]

Maybe we should remove 640x480x16 limitation?
I did some preliminary research. It looks like "vgapnp.sys" should support VESA sompatible SVGA, i.e. at least 800x600x256 Also I found that txtsetup.sif has [Map.Display] and [Display.Load] sections that define "initial"graphic driver.
So far, I still don't know how to specify resolution and color depth

Alexei

800x600x256 would be a better foundation to work with.

[TheHive]

My two cents, OK, three:
1) I would keep the "Boot Land" logo, without the "trailing" USB and CD, making it a little smaller and adding under it, in small characters "our" address www.boot-land.net
2) The monitor looks too "flat", expecially the stand of it, I would try to make a perspective image, something like this:

(you know how much I suck at graphics )

3) I would keep the WinBuilder reference inside the monitor, and let go the Copyright , let the lamers have the image if they want it.

jaclaz

[Alexei]

jaclaz
I found bootvid.dll clone (with source) on http://www.tinykrnl.org/ (in their sources).
Can it be used to alternate boot logo (legally)?
Can we make it work with 800x600x256?

Alexei

[was_jaclaz]

@TheHive
Last image is perfect, as I see it!


@Alexei
VERY GOOD find!

Can it be used to alternate boot logo

Yes, you just call it "Unofficial Service Pack for Bootscreens" and everything is OK!

Can we make it work with 800x600x256?

That I don't know, I am sure that the basic vga.sys can have 800x600, but I don't know how to "pass" the setting when booting.


Alexei, while we are talking, [COMPLETELY OUT OF TOPIC] can you have a look at this thread and tell me what do you think about it:
http://www.911cd.net...showtopic=18650

or maybe there is something in the site you found about my old idea of having a NTBOOTDD.SYS to access USB devices:
http://www.911cd.net...o...c=18654&hl=

jaclaz

[TheHive]

That is a good find Alexei

If you want to look at the layout compared to NTs.
http://www.tinykrnl.org/dev_source.htm

If you read on there webpage it tells you to look in the download section but since they are upgrading they dont have anything there yet. But if you want to download the source or the nightly build look at the top of the site where it says Nightly Release to download a file called tinynightly.7z. In the tinykrnl\base\boot\bootvid
directory you will find the files. I cant mess with it because I dont know how to compile it or whatever it needs to be done for it to work.

In rereading your post you mention you found the bootvid.dll. Where can it be found.

You think we might be able to use other files from the project?

@TheHive
Last image is perfect, as I see it!
jaclaz

Ill clean it up some more.

[Alexei]

@Alexei
VERY GOOD find!

@jaclaz
Can you compile and try it?
I didn't dig deep, but it seems bootvid just passes drawing commands from kernel to display driver.
It's not clear to me how it all works Do you know how (in general)?

[COMPLETELY OUT OF TOPIC] can you have a look at this thread and tell me what do you think about it:

@jaclaz
I read the forums (not every word, though). This kind of talk is going on for about 3+ years on many forums, but w/o any real outcome
Initially, I was also thinking about NTBOOTDD. Though it may solve some problems (especially with big HDs) it needs it to be loaded, which is not possible without correct geometry provided by BIOS. If you had experience with really old PCs (before IDE autodetect) you know that HD geometry had to be entered manually. It was common case when IDE drive could be r/w, but not booted until you specify "magic numers" in BIOS setup Even now this may happen when you try to boot from mirror drive (it was MS KB on that). I think you may have success booting with Grub, loading SDI image, and booting from it
Though, I don't really know what is your goal
Contrary HD, USB CD should always boot
Here http://bootcd.narod.ru/index_e.htm you can find some CD boot managers
In addition, running "real" XP/W2K/2003 from USB has to deal with BSOD 7B.
7B happens because of two reasons: 1. MS setup doesn't allow installation on USB HD, so you have to use IDE (or SCSI) and then copy files or use USB enclosure. 2. By default, USB drivers are not loaded at boot time. So you have to "fix" the registry to assume another boot drive and make USB drivers start earlier. Dietmar did it, which stopped my efforts in the same direction. I may return to this area later having better knowlage about boot and setup process, as my ultimate goal is "portable windows" BTW, Dietmar's XP will not boot from any PC
jaclaz, can you send me PM so we could continue this discussion without disturbing others?

[Alexei]

That is a good find Alexei
...
You think we might be able to use other files from the project?
Ill clean it up some more.

It's under \base\boot\bootvid\
Of course, I downloaded it and took a look before posting (for.ex. the one from ReactOS is incompatible).
Initially, I was thinking about writing replacement that would use BIOS VESA calls, so I was looking for interface (calls/parameters) description In bvstatus.txt I found all calls are "implemented", so it may actually work (not sure, though). If not, there is another (legal) trick: to rename source DLL and write DLL with same entry points that would load original, (patch it in memory if necessary), then transfer calls to the original modifying data passed in both directions. This way you can do whatever you want, I know
And just for fun, look what I think may be a base for alternative WB logo.
Initially I "digitized" it to be suitable for 16 colors, but then I found it funny
"Created with WinBuilder" suppposed to be placed over

Alexei

Attached Thumbnails

• 

[TheHive]

[was_jaclaz]

@TheHive
Super!

@Alexei

Can you compile and try it?

No, sorry I don't even KNOW what a compiler is, seriously I never learned using them, I don't understsnd anything of C, C+ or C# (How someone could call "sharp" the dumber laguage I've ever seen, still is a mistery for me) and I am unfortunately to old to learn it.

jaclaz, can you send me PM so we could continue this discussion without disturbing others?

I'll start a new thread on the subject, as soon as I have gathered some more info on another possible approach I just found.

Thanks for your interest in the matter.



jaclaz

[Alexei]

@jaclaz
I do all my dirty tricks in Delphi (with a bit of assembler, sometime)
I also like to struggle with limitations of cmd scripting
Writing DLL is not abig deal, but first I have to overcome networking

Alexei

[TheHive]

Here is the BMP:
 bootupScreen.zip   53.06KB   324 downloads

[phox]

Here is the BMP:

This is it!!!

For the sake of graphical balance, please move
the monitor and Boot Land logo a little to the right.

Bring back Nuno’s Copyright to the screen,
to synchronize it with Boot Land logo on the top!

Without that, there will be too much of a Boot Land
and nothing of Nuno, what is not acceptable!

[TheHive]

I moved the Bootland part a bit to the right. It looks better.
I cant move the display more to the right because it patching a other colors in the CD from showing up.
I dont think that we need a copyright within the image. Winbuilder should be enough for a person that sees it to be able to get an idea of the message the screen on the LCD is portraying.



BMP:
 BootUpScreen.zip   53.74KB   338 downloads



BMP:
 BootUpScreen1.zip   47.84KB   331 downloads

I'm going to create a script to change the boot-logo .

any update on the Script

[smiley]

@ TheHive: Everytime i edit Sherpya's dll, my build fails. Can you edit sherpya's bootvid.dll and attach it?

[TheHive]

Both of the above in its own bootvid.dll

 bootvid.dll.zip   113.57KB   355 downloads
Can you add both as an option and also the ability for someone to select their own bootvid.dll if they have one.

[smiley]

Why don't you create a script for this?

[phox]

I moved the Bootland part a bit to the right. It looks better.

The first picture is the best solution!, but...

The Hive,

you know that high value your work and opinion
and please don't take this personally.

I don't agree that we omit Nuno's WinBuilder Copyright.

Without Nuno there would not be Open/WinBuilder and Boot Land Community.

Participation of Boot Land Community is clearly displayed on the top of the picture
and Nuno's Copyright must be below WinBuilder title on the screen!

Kind regards, phox.

[Alexei]

The first picture is the best solution!, but...

The Hive,

you know that high value your work and opinion
and please don't take this personally.

I don't agree that we omit Nuno's WinBuilder Copyright.

Without Nuno there would not be Open/WinBuilder and Boot Land Community.

Participation of Boot Land Community is clearly displayed on the top of the picture
and Nuno's Copyright must be below WinBuilder title on the screen!

Kind regards, phox.

Dear phox,
What copyright you actually mean?
- on the picture
- on WinBuilder software
- on WinBuilder name
- on BootLand logo
I believe, Nuno deserves highest appreciation as the founder and leader of BootLand/WinBuilder community. That's why you should have asked his approval before requesting to add his name to the picture.
Alexei

[phox]

Dear Alexei.

Please, I really don’t need your “lectures”
and kindly ask you to avoid them in the future.

Kind regards, phox.