Jump to content











Photo
* * * * * 1 votes

New VPELDR.exe - testers wanted


  • Please log in to reply
58 replies to this topic

#26 PaPeuser

PaPeuser

    Silver Member

  • Advanced user
  • 787 posts
  •  
    United States

Posted 28 January 2009 - 05:42 PM

:cheers:

Thanks for pointing that out , i got lost with version 2 and trying to figure out how to unpack and pack ,,

#27 risolutore

risolutore

    Frequent Member

  • Advanced user
  • 311 posts
  •  
    Italy

Posted 28 January 2009 - 05:44 PM

Thanks, maybe solved :cheers: I will wait future beta in order to test it.

#28 pecd.net

pecd.net

    Silver Member

  • .script developer
  • 947 posts
  •  
    Germany

Posted 28 January 2009 - 07:10 PM

@amalux

i think i know where your problem comes from and it will be solved with the new (planned) hardware detection...

#29 e2p2

e2p2

    Member

  • Members
  • 51 posts
  • Location:NC, USA
  •  
    United States

Posted 28 January 2009 - 07:23 PM

CTMAG,

Do you have any idea why the start menu is not displaying correctly with your VPELDR?

#30 dera

dera

    Gold Member

  • .script developer
  • 1335 posts
  •  
    Hungary

Posted 28 January 2009 - 07:23 PM

And just want to point out that I can NOT do that with version VistaPE (RC1) WB [075 beta 5K]

Don't use the '075 beta 5K'!
that version mess up the whole .script when you try to handle the script's attachments

#31 e2p2

e2p2

    Member

  • Members
  • 51 posts
  • Location:NC, USA
  •  
    United States

Posted 28 January 2009 - 07:30 PM

You should use the latest version, CTMAG has a download link in his signature. Currently the most recent version is 075 beta 6 e.

#32 pecd.net

pecd.net

    Silver Member

  • .script developer
  • 947 posts
  •  
    Germany

Posted 28 January 2009 - 07:48 PM

@e2p2
with the current version it should display OK, are you sure it still does not? can you post a screenshot?

#33 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 28 January 2009 - 08:11 PM

@amalux

i think i know where your problem comes from and it will be solved with the new (planned) hardware detection...

:cheers:

#34 e2p2

e2p2

    Member

  • Members
  • 51 posts
  • Location:NC, USA
  •  
    United States

Posted 28 January 2009 - 08:27 PM

@ctmag
I just double checked and rebuilt VistaPE. I am using the most recent version of VPELDR you have linked to in post#1. Here is the screen shot showing the start menu.
menu.jpg

#35 pecd.net

pecd.net

    Silver Member

  • .script developer
  • 947 posts
  •  
    Germany

Posted 28 January 2009 - 08:53 PM

OK, i will recheck...thanks for the report...

#36 PaPeuser

PaPeuser

    Silver Member

  • Advanced user
  • 787 posts
  •  
    United States

Posted 28 January 2009 - 09:03 PM

hello EDITED this post should have been before post 34 , i am a slow

see if i have this right

download from CT's signiture newest Winbuilder [075 beta 6e] and
from download Servers in Winbuilder download VistaPE
Download PEloader from post #1
unpack and pack new loader then test

and test and report,,

am i OK so far??

#37 PaPeuser

PaPeuser

    Silver Member

  • Advanced user
  • 787 posts
  •  
    United States

Posted 28 January 2009 - 10:36 PM

Ok test 1 (all new WB [075 beta 6e and VistaPE 12 downloads and VPELDR from post 1)

PEloader takes a long time at Installing Network - wpeinit.exe
Network card needs to be installed before networking?
This maybe why PEloader is slow installing networking?

BS Shell
Start menu is still not right
No network

EXPLORER Shell
Menu Items work well
No networking

Device Manager
Network card is not installed (unknown device)

Plugged in before boot
All USB hard drivers are detected and installed correctly
Old USB keyboard and mouse are detected as Silitek USB Keyboard and not installed correctly
(this is old Gateway USB keyboard that you plug USB mouse into)

After boot
USB wireless logiteck mouse was detected as USB receiver but NOT install
USB hard Drives were Not installed and listed correctly

#38 dera

dera

    Gold Member

  • .script developer
  • 1335 posts
  •  
    Hungary

Posted 28 January 2009 - 10:49 PM

I have the same problem with BS Explorer's Start Menu as e2p2 reported at Post #34

#39 PaPeuser

PaPeuser

    Silver Member

  • Advanced user
  • 787 posts
  •  
    United States

Posted 28 January 2009 - 11:28 PM

Have you tried to view Device Manager or use Explorer Shell?

Hardware and USB detection was the major problem that started all this.


I have the same problem with BS Explorer's Start Menu as e2p2 reported at Post #34



#40 dera

dera

    Gold Member

  • .script developer
  • 1335 posts
  •  
    Hungary

Posted 28 January 2009 - 11:59 PM

Didn't try the Explorer Shell.
The truth is at me the old vpeldr.exe worked fine, at me there was no hardware detection problem,
plus if I didn't interrupt the fast hardware detection of vpeldr I was able to load driver after boot from the external 'Drivers' folder or e.g. from USB stick using drvload.exe devcon.exe or hwpnp.exe
(also the slow hardware detection worked at me),
now with the newer version I have no success.
Seems only that drivers are loaded what was integrated at the build time with the help of the peimg.exe (or what is already integrated by Microsoft)

#41 PaPeuser

PaPeuser

    Silver Member

  • Advanced user
  • 787 posts
  •  
    United States

Posted 29 January 2009 - 12:14 AM

For a long time I used only BSexplore

Now I have come to like Explorer Shell

When we test drivers or hardware detection you almost have to build a CD or USB stick and boot to it

Plug and unplug USB devises notice how they are detected and if drivers are installed right

Biggest problem is USB keyboards and mice not being detected or installed correctly at boot time.

I am sure menu will be fixed ASAP… LOL

EDITED so i test both BSexplorer and Explorer Shells
i also was one who had lots of luck with USB devices and
could not figure out why everyone else was haveing trouble with usb keyboards and mice.
till i tried a few different usb keyboards and mice

#42 e2p2

e2p2

    Member

  • Members
  • 51 posts
  • Location:NC, USA
  •  
    United States

Posted 29 January 2009 - 12:19 AM

@dera

If you had carefully read the beginning of this thread you would see that this VPELDR was written to not autodetect hardware. Some of us where encountering problems resulting from the original VPELDR autodetecting hardware. If you want to use this VPELDR and you have not integrated the drivers you need you will have to run a device detection program like HWPNP.

#43 PaPeuser

PaPeuser

    Silver Member

  • Advanced user
  • 787 posts
  •  
    United States

Posted 29 January 2009 - 12:30 AM

After boot even running HWPNP or slow detect in peloader did not always help
and how can you run either if your USB mouse was not detected at boot??

#44 e2p2

e2p2

    Member

  • Members
  • 51 posts
  • Location:NC, USA
  •  
    United States

Posted 29 January 2009 - 01:01 AM

@PaPeuser
Ah, but that's where the VPELDR and one other thing help (http://www.boot-land...opic=6732&st=20). After I had used the info in that post, and added the VPELDR, my USB mouse and keyboard started working on my Poweredge 1950.

#45 PaPeuser

PaPeuser

    Silver Member

  • Advanced user
  • 787 posts
  •  
    United States

Posted 29 January 2009 - 01:12 AM

Ok that help you But CT's looking for a fix for everyone.
Why do some Human Interface (USB) Devices install correctly and other not?

try a few different computers and USB keyboards and mice, they all should work!

right out of BOX or with out other script

#46 PaPeuser

PaPeuser

    Silver Member

  • Advanced user
  • 787 posts
  •  
    United States

Posted 29 January 2009 - 01:34 AM

you mean this post helped you ???

http://www.boot-land...?...=6732&st=20

did you ever let CT know it worked for you???

#47 e2p2

e2p2

    Member

  • Members
  • 51 posts
  • Location:NC, USA
  •  
    United States

Posted 29 January 2009 - 03:35 AM

I meant to but have not yet, I will try to tonight.

#48 pecd.net

pecd.net

    Silver Member

  • .script developer
  • 947 posts
  •  
    Germany

Posted 29 January 2009 - 06:12 AM

Just to make it clear: the USB keyboard/mouse issue needs this fix http://www.boot-land...?...ost&p=56496

the new vpeldr.exe is not really to adress this problem, it is for all other hardware issues:-)

Not working hardware (like network cards) and wpeinit taking long to install network is a side effect that will be fixed...for now i need to know what happends when using the new loader so i can decide which way to go...

Please make sure you build your pe to use multiboot or standard in ram option, do not select "direct from disc" option...this sometimes causes network starting issues, too

#49 dera

dera

    Gold Member

  • .script developer
  • 1335 posts
  •  
    Hungary

Posted 29 January 2009 - 11:04 AM

@dera

If you had carefully read the beginning of this thread

Yes I had read carefully

you need you will have to run a device detection program like HWPNP

f you had carefully read my Post #40 you would see
this is what doesn't work at me using the newer version of vpeldr.exe

#50 pecd.net

pecd.net

    Silver Member

  • .script developer
  • 947 posts
  •  
    Germany

Posted 29 January 2009 - 11:12 AM

For now this experiment stops here....nightman wrote he is working on something new, so it is a waste of time to play around with vpeldr.exe now...lets see what he comes up with...give it a few more weeks...




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users