No new boot screen in Aspire One with 6956.

[cron]

I just installed build 6956 in my Aspire One, and everything is working wonderfully. I even think it runs a little faster than the 6801 build.

But I was really looking forward to seeing the new animated boot screen (I'm a sucker for presentation in software), and was utterly dissapointed to see the same Vista-like loader. I was just reading about the animation being a video or something like that.

So, is it possible my netbook can't display the new boot screen because of the "handicapped" video performance, or do I have to enable it?

 

[johngalt]

Hi, cron, and welcome to the forums.

I am assuming you have run the BlueBadge v3 tool? I do not know if that has anything to do with it as I cannot get 6956 to run on my machine, but it may....

 

[cron]

I haven't thought of that before, so I applied it. And no, still no new boot screen. Thanks for the quick reply though.

Anyone with other netbooks trying the 6956?

 

[darkassain]

do you know which build your aspire is (110 or 150) ???

i think it is because you do not have the wddm (Vista drivers or W7 drivers) drivers you have the XPDDM drivers since the website does not display any vista drivers....

just looked and i see no vista supported drivers.....


but that should not be it because in vmware it loads up correctly
how much mem does your aspire one have???

i have only heard of this when you try to change the boot image files (like trying to change your boot screen)...

 

[baarod]

You don't get the nifty boot screen w/o the new 200GB partition. To be sure and get that backup and repartition the boot drive so there is at least 50GB empty space at the start of the drive and the install 6956 into that empty space. Do not create a partition.

 

[darkassain]

@baarod
ummmm, you actually do get it as i have manually created in the (w7 installation and pre installation) the partitions and it loaded up perfectly (well when i had it...lol)

i reformatted at least 5 time and it worked perfectly.....
something wrong on your end????

 

[baarod]

did you get the 200MB boot partition at the start of the drive?

 

[darkassain]

@baarod
if you are asking me see below if not then ignore the post
i manually create my partitions so i overide that scripted event....

if you go to advance options you can create your partitions without having to have the 200mb partition

the first time with 6956 i did the regular way...
did it and the boot screen worked
i reformatted and then instead i formatted my partitions in W7 installation manually
still worked
i did a third time and instead formatted the partition with Vista and it worked also....
the rest was because of malware...lol

 

[Bare Foot Kid]

Hello cron, welcome to Se7en Forums!

You can see the new 6956 boot image here.

Windows 7 Forums - Windows 7 Build 6956 new animated boot screen video














Later :shock: Ted

 

[Mindstorm]

Hi Cron,

I've installed the 6956 build on my Lenovo s10 netbook, didn't get the new boot screen either. I guess you've used the modified ISO install as I did. You will never get the boot screen using that install as it uses the 6801 files until you get booted to the desktop...

It's a bummer, but at the least we got a simple install using a DVD

 

[darkassain]

i did a dvd install so there should be no problem with that...
that is weird...
maybe your iso was modified in some other way???

 

[johngalt]

Again,l unless you format the HD *completely* and use the unpartitioned space for the entire thing to use to install W7, you won't get the 200 MB boot partition. According to others earlier, without that 200 MB partition, you don't get the new boot screen.

 

[Bare Foot Kid]

Again,l unless you format the HD *completely* and use the unpartitioned space for the entire thing to use to install W7, you won't get the 200 MB boot partition. According to others earlier, without that 200 MB partition, you don't get the new boot screen.

I don't believe this is has anything to do with it; because when I install 6956 it goes on the first partition on a HDD that already has 6801 on the second partition on the drive and I still get the new boot image.








Later :shock: Ted

 

[baarod]

Worked for me with 6801 installer overlaid with 6956. Just make sure to boot off the DVD and let the installer create it's own partition -- i.e. don't install into an existing partition. That might not be the only way to get the new boot screen but its worked flawlessly for me on two notebooks, a desktop and a media center machine.

 

[Bare Foot Kid]

When I install 6956 it goes on the first partition on a HDD that already has 6801 on the second partition on the drive and I still get the new boot image.

I've installed 6956 on to an existing partition three or four times and I get the new boot image every time. I boot from the DVD, format the existing partition then let the installer finish and the new boot screen is there every time.









Later :shock: Ted

 

[linuzo]

I don't think it has anything to do with your partitions, video or ram. This is a boot screen people it's not video accelerated. It isn't even in the OS yet!! All it is a animated boot screen just like the other one that use to animate across the screen then it was loading instead it is a different image.

I would say to check your ISO, I think the version of windows 7 you got could have been modified or perhaps it's still 6801 with some minor changes from someone on the net. If I were you and your going to get the 6956 version then you should try to get it from a legit source like WinBeta or another known source that sometimes leaks beta's to the public. I cannot give you a torrent since it is piracy. However we can provide some tips on how to tell if your version is a true 6956 or not.

IMO, I think people should wait for 7004 to be released in January so we can all have it.

 

[Mindstorm]

So, how can I verify that I have a "true" 6956 build?

I installed from a bootable DVD to a new and fresh HDD, I used gparted to create one 40gb partition for my WIn7 install, the rest 450gb is a "data" partition. Would my choice of size for the install have any thing to do with it? More than half of the 40gb is still unused...

 

[baarod]

Is the 40GB partition at the beginning of the disk or elsewhere? Have you tried installing into free space rather than creating a partition with gpartd first?

 

[darkassain]

@mindstorm
do a sfc /purgecache (this will purge the cache so that it in case the have tampered with the cache) (of course on the after installation)
sfc /scannow


if you do get it scanned correctly and you are still in doubt like linuzo said
get a download from a trusted group like winbeta or Orbit 30
(of course look at if any comments on the download and choose based on this and how trusted the distributor is)
i do this and have not have had any problems at all

I installed from a bootable DVD to a new and fresh HDD, I used gparted to create one 40gb partition for my WIn7 install, the rest 450gb is a "data" partition. Would my choice of size for the install have any thing to do with it? More than half of the 40gb is still unused...

there would not be any difference where it is installed like linuzo said it does not matter where its installed....

the only reason i see that it would revert to the vista bootscreen is when some hash does not check out (tampering/modifying of the boot files )

 

[TheOnlyValidReason]

you guys are missing the point

well according to people that wished not be mentioned here, the beta builds for the vienna/blackcomb/seven are mainly done on 1024x786 monitors, to ensure more compatibility with old hardware (where vista failed) the loading screen from vista is still included in beta and pre beta builds to cater for those with lower screen resolutions. yes the new neutron bootscreen is in fact a raw video, sorta like the oldschool BINK video format, which will only run when the prerequisites are met. for netbook users, wait for the netbook version of W7 optimized for ssd's and small screens, and to the others, there is no such thing as no new boot screen without the 200mb partition. the 200mb partition was implemented to cut down on piracy as it will inhibit the usage of 3rd party bootloaders to pre activate windows (which is now slp2.0 proof)

this is just a hardware issue, some dudes over at (netbookforum) *name n url held by request* is trying to figure out the format of the bootscreen from the boot load mui files and are trying to port them to vista/W7 for smaller screens.

waiting is a fun game. its worth the wait. trust me.