Not burned it to CD yet, but just mounted it with daemon and deepburner appears twice.

It's in the CD Burners and Applications.

Due to Deepburner having 2 plugins:

plugin\aspi\deepburner V1.1.5
plugin\deepburner V1.5.1

crap, figured I missed something

Well at least it's nothing major

I've now loaded the CD.

Linux Tools is missing, can't find it anywhere.

On Networking Tools, the menu appears to be missing something from the top or it's been formatted incorrectly.

Apart from that it seems OK.

There are no dat files in the "Mcafee folder" and I can't seem to get them installed, because I don't really know how to do it. I have tried opening the dat file download in the files folder, but the wizard says there is no program to install it in...

Steel,
I'm still having the USB error I told you of last night. This is a completly clean 2.5 build with driver version 1.0. If I click into "Plugins" and then try to click "Close" to close the plugin window (without making any modifications), I get this:



If I disable the plugin:
System: USB & IEEE1394 (Firewire) V2.4c

I don't receive the error.

Just got home from work. I realized the mistake when I got up for work this morning, I really wish I would have had time to fix it then. Sorry everyone big mistake here. Man I really messed up. I was trying a new usb plugin from someone else, it's supposed to be better than the old one I had.

Well, I forgot to change a few things. So I am going to figure out a fix really quick and upload a few files to my server. Everyone will be able to get the fix for the usb plugin and I'm going to seperate the firewire plugin from it, currently it's a combination usb & firewire.

Please give me 1/2 hour to hour and I'll have a fix released. I'm going to post a message on the site and take down the download for the time being. Then I will release the fixed version and a small "fix" file for everyone that has already downloaded.

Well at least there wasn't anything seriously wrong. Most people I don't think would even notice.

They should. I took the download down when I got home. The fix is really easy. I will upload the new new fixed usb plugin as a seperate download. The user will then simply delete the old plugin, delete the extra "deepburner" plugin located in the "aspi" plugin, and then extract the usb plugin in their "plugin" folder.

I'm still trying to figure out how I ended up with an additional deepburner plugin in my build???

I haven't actually had a chance to run and test the CD, but when I built it last night with the new version, everything went fine, no errors and ISO was built. Seems strange to me... :-\

You must have a firewire card then Littlbuger

If I'd have built the CD at home I would have got the errors as I don't have a firewire card in my home PC, didn't install it as I don't need it.

OK, burned 2.5 with drivers 1.0. It all worked well. Only thing that I found so far was that CWshredder does not start. That might be because I've added the new True Image plugin. Very nice job as always!!!

Edit: the FTP site for updating the definitions for TrendMicro's Sysclean seems to be invalid. I FTPd there myself and it seems to be empty.

another issue I found was that the application Keyfinder is still in the System Tools menu which doesn't exist anymore. Which means there isn't a shortcut for this application.

System Tools and the Keyfinder shortcut are there on mine!

beenthereb4


You should not because this menu option was removed from the new menu structure.

Keyfinder. It's not on mine. It's a pretty easy fix though. Just modify the XML file for the plugin.
CWShredder is still being a pain! I haven't been able to figure out how to get it to work in PE. Once things slow down a bit for me I will start working on figuring out how to get it to run again!!

DeepBurner. I thought I had it working before but it also does not work at the moment for me either. DeepBurner is a new version, maybe they added more dependant registry entries? I will research that more and see if I can find a quick fix for it.

Sorry about that guys and gals.

I've already updated the trend micro plugin.

I posted about it here.

Trend FTP site

Download Updated Plugin here

Hi,

Great job as usual Ben, the new menu layout makes it a lot easier to find the app you need.
I have not had a chance to try many of the apps as yet but the new MMC looks interesting.

One thing that I have found that does not seem correct, is that there is no EXIT in the menu. This is required to cancel Nu2menu after use, when the disk is autostarted from within Windows.

This line should be in the nu2menu.xml file at the bottom of the Startmenu section :

<MITEM TYPE="ITEM" DISABLED="@FileExists(@GetWinDir()\setupldr.bin)" CMD="EXIT">Exit</MITEM>


Another thing that I'm not sure on is an issue with HHCTRL.OCX.
Has any one reported issues with Izarc at all ?
I ask because Izarc uses the file hhctrl.ocx (active X control), this is in the sys32 folder of the Izarc plugin.
The thing is that the Viewchmhlp plugin also uses a hhctrl.ocx file but this one is a 'spoof' version used in its operation. As this plugin is processed after the Isarc plugin, this is the file that that ends up on the disk. So Izarc does not have the correct hhctrl.ocx file to work with.
I have not used Izarc, so I would not know if it works fully or not.
This came to light when I was testing another freeware compression program which also requires hhctrl.ocx. The program would not start as all it could find was the 'spoof' hhctrl.ocx file. I had to disable the Viewchmhlp plugin to get the compression program running. This would have been the same in the 2.4x versions as well.

The last thing is a small sugestion that you may wish to use in the setting up of the disk. If this INPUT.INF is placed in the build folder, you will have a default setting of UBCD4WIN25 for the disk label, the output folder and the ISO name.



[LicenseAgreed]

[input]
verbose=0
ISOduplicatesonce=0
skipfiles=0
skipregistry=0
buildiso=1
burncd=0
blankcdrw=0
burnonthefly=0
useAbsoluteOutput=0
customdir=
isofile=UBCD4Win25.iso
outdir=UBCD4Win25
fulloutdir=
source=
volumeid=UBCD4Win25
device=



Snowtime

@stidyup
Well, thanks, but I still had to change the code (copied from your post) as follows:

Hi Ben,

As the Keyfinder plugin has an error in the path and does not show in the menu system. Also the fact that KeyfinderPE does not work under a running system. I thought you may be interested in this modified one. This uses both Keyfinder and KeyfinderPE. When the disk is running from boot the KeyfinderPE option is available. When the disk is autostarted from within Windows the Keyfinder option is available.
Just go to http://www.magicaljellybean.com/keyfinder.shtml and get the full version of Keyfinder. Then put it in your keyfinderpe plugin folder along with the files below.

KeyfinderPE.inf :-


; KeyfinderPE.inf
; PE Builder v3 plug-in
; Created by
; http://www.ubcd4win.com

[Version]
Signature= "$Windows NT$"

[PEBuilder]
Name="KeyfinderPE"
Enable=1

[WinntDirectories]
a="Programs\KeyfinderPE",2

[SourceDisksFiles]
KeyfinderPE.exe=a,,1
keyfinder.exe=a,,1

[Append]
nu2menu.xml, KeyfinderPE_nu2menu.xml



KeyfinderPE_nu2menu.xml :-


<!-- Nu2Menu entry for Keyfinder PE -->
<NU2MENU>
<MENU ID="Password Tools">
<MITEM TYPE="POPUP" DISABLED="@Not(@FileExists(@GetProgramDrive()\Programs\keyfinderpe\*.*))" MENUID="Keyfinder">Keyfinder</MITEM>
</MENU>

<MENU ID="Keyfinder">
<MITEM TYPE="ITEM" DISABLED="@Or(@Not(@FileExists(@GetWinDir()\setupldr.bin)), @Not(@FileExists(@GetProgramDrive()\programs\keyfinderpe\keyfinder.exe)))" CMD="RUN" FUNC="@GetProgramDrive()\Programs\keyfinderpe\keyfinderpe.exe">Keyfinder PE</MITEM>
<MITEM TYPE="ITEM" DISABLED="@Or(@FileExists(@GetWinDir()\setupldr.bin), @Not(@FileExists(@GetProgramDrive()\programs\keyfinderpe\keyfinder.exe)))" CMD="RUN" FUNC="@GetProgramDrive()\Programs\keyfinderpe\keyfinder.exe">Keyfinder</MITEM>
</MENU>
</NU2MENU>

I put the entry under Password Tools as the System Information tree is rather a long one already.

Snowtime

On mine, I added "Device Manager Clone". This must have caused "System Tools" to appear. Then under "System Tools", I have On Screen Keyboard (Which I did not add) and KeyfinderPE (which I did not add or modify) and of course Device Manager Clone. Go figure!

You know what.....I was thinking about the "onscreen keyboard" the other day. It just popped into my head at work, I didn't remember seeing it anywhere. By the time I got home from work I totally forgot about checking into it. I'm going to have to go over my notes for the new menu structure and figure out how I missed two tools (that I know of so far).

Hi Ben,

As you have some things to alter on the new disk, this is just a tidy up item.
In the Geoshellv2 folder there are four CMD files that are now redundant as you have implemented the new screen setting mod.
These are :-
files\SetResGeoshell640x480.cmd=2
files\SetResGeoshell800x600.cmd=2
files\SetResGeoshell1024x768.cmd=2
files\SetResGeoshell1280x1024.cmd=2

In the Geoshell.inf and the same items in the files folder.

I did not mention these in the mod post as they are not doing any harm there.

Snowtime

Can't find Spybot on mine, and get a disk is full error when trying to run Firefox. Anyone else having this problem?

SpyBot has been removed, it will NOT work in PE. Sorry, I kept it on for a few months but no one else nor myself could get it to work properly.

FireFox??? There have been no reported issues with FireFox, what exactly is happening??

Your RamDisk is full.

How much ram do you have on the system?

As lawson23 said, your RAMDisk is probably full. How much RAM do you have in your system and what size of RAMDisk did it create? Have you tried the Clear RAM Drive menu option before running Firefox?

The system has 512, when it was created it said it made it 20meg, and yes I did try the clear ram and still same result. Is there a way to force it to a larger size?

20MB??? Mine usually creates a 140MB or so RAMDrive with my machine that has 512RAM. That's really strange... I think there's a problem elsewhere here... Does everything else work? Any errors elsewhere?

The project is now using the ramdriver from Bart's BETA, I think I read there are some limitations to it just like the other ramdriver. However this ramdriver doesn't "popup" donation requests, etc.

I think 20Meg should be enough for FireFox, it's not that big of a program and it doesn't hog up that much!!

Hi,

The new Ramdriver has a limit of 96Meg in size, regardless of the amount of ram in your system. With your 512Mb of ram you should have a 96Meg ramdrive setup at startup time. But you say it only setup a 20Meg one?
On my systems here they all have the correct proportions to the amount of ram installed, but there may be an issue with the AutoRamResizer app and the new ramdriver.
FireFox is using 18.2Meg on my ramdrive here, this is quite a chunk of the ramdrive!
This needs to be looked into further I think.

For your problem you could try going to the ramdisk folder and open the file ramdisk.inf.
You will see the lines:-

[Strings]
RamDiskDriveLetter="B:"
; Approximate
; Ramdisk Hex
; Size Value
; 32 megs. 0x02000000 (default)
; 64 megs. 0x04000000
; 96 megs. 0x06000000
; 128 megs. 0x08000000
RamDiskDiskSize="0x02000000"

Try setting one of the higher numbers and then rebuild and see if it is any better.

Snowtime

2 other minor issues.

One relates to a fix posted for the sysclean plugin in the 2.5 fix post.
The xml file reads <MENU ID="Programs"> It should read <MENU ID="AntiVirus Tools">.

Second one is to do with the XSP plugin. This plugin should show in the Registry Tools menu and shows under Programs.

How to fix this is to modify the xml file found \plugin\XSP\files\cfg\bpe_xsp_menu.xml to say <MENU ID="Registry Tools"> instead of <MENU ID="Programs">.

Yeah, I didn't realize the error in the New Sysclean plugin until yesterday. I downloaded it from Stidy, he emailed it to me, and thought he already had it set for AV tools. Sorry about that, it's totally my fault for not checking the file.

The XSP plugin, I dunno I forgot about that one too. I will be trying to find time during the next few days after work to try and get more work done on these issues and release 2.51 within a few weeks. It just really ticks me off that all of these errors exsist, all the hours I spent working on the new version and I still missed stuff?