The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Black Screen before log in screen (windows 7)

    Discussion in 'Windows OS and Software' started by thedj, Jul 20, 2010.

  1. thedj

    thedj Notebook Guru

    Reputations:
    0
    Messages:
    61
    Likes Received:
    0
    Trophy Points:
    15
    Hi, I have a Samsung R620 Laptop, it has 4GB Ram, 2.1 GHz processor, 500GB HD

    and I just formatted my pc and installed windows 7 64 bit back on to it, but now when I start my laptop, I get a black screen where I can see the cursor only for a few seconds and then it shows the log in screen, does anyone know how to remove this black screen and make it go straight to the log in screen?

    I have already tried the following

    opening Run and typing msconfig, then go to boot, then advanced and changed the number of processors to 2, and ticked maximum memory.
     
  2. lbohn

    lbohn Notebook Consultant

    Reputations:
    320
    Messages:
    235
    Likes Received:
    0
    Trophy Points:
    30
    http://www.withinwindows.com/2008/0...rformance-for-multi-core-users-with-msconfig/ "Die evil myth. Die."
    This option is useful for limiting memory. Enabling this option and setting it to equal your physical memory will have zero improvement over the default, disabled setting.

    Since you are already blindly mucking about in msconfig, you will find better boot time savings disabling startup programs in the Startup tab. Startup Assistants and Quick Loaders are typically great candidates for getting the axe. Be careful, however, you can render your system unbootable.

    --L.
     
  3. pstrisik

    pstrisik Notebook Evangelist

    Reputations:
    81
    Messages:
    324
    Likes Received:
    0
    Trophy Points:
    30
    I think this is normal. I've had a second or two of black between the windows logo screen and logon screen with both XP and Win7.
     
  4. thedj

    thedj Notebook Guru

    Reputations:
    0
    Messages:
    61
    Likes Received:
    0
    Trophy Points:
    15
    Actually this increased the speed of logging in, first when I had it set to 1 processor, when I typed in my password, it took 35 seconds for the Log in screen to show my desktop, after changing it to 2 processors, it taks 8 seconds, wow what a big improvement!

    I am offended after reading this, Im not blindly mucking about in msconfig, I used msconfig on various occasions before, and I clearly know what im doing and what can and cant mess up my boot.
     
  5. cloudbyday

    cloudbyday Notebook Deity

    Reputations:
    50
    Messages:
    706
    Likes Received:
    0
    Trophy Points:
    30
    You can download Puran Free Defrag, and it will defrag the startup files. It may or may not fix it for you.
     
  6. lbohn

    lbohn Notebook Consultant

    Reputations:
    320
    Messages:
    235
    Likes Received:
    0
    Trophy Points:
    30
    It was never my intention to offend: mea culpa.
    And of course it would: you first limited then removed the limit on cores for the boot process.

    In your first example, "when I had it set to 1 processor", you limited the boot process to a single processor. "[A]fter changing it to 2 processors" you used both of your cores and had a significant improvement. However my original point stands: setting the processor count to 2 (on a dual-core system) is the same as disabling this option, the default setting.

    Microsoft KB article (from the linked posting):
    The default setting in Windows (XP, 2003, Vista, 2008, 7) uses as many cores as are available during the boot process. If you have 2 cores, Windows boots using both cores. Unless your system was configured "out-of-the-box" to only use 1 core by the manufacturer, you are not enabling "unused" cores in the boot process: by default all cores are already being used.

    --L.