The 911 Rescue CD new release is ready for public release, but it needs some beta testing process before it is officially out, if anyone is willing to participate in this Beta testing program, contact me via email, so I can send you a link to the new CD Builder release (no PMs please).


Here is a summery of additions/enhancements in this release :

911 CD Boot Menu:
- Using the new CDShell scripts (a new version of the 911 CD Menu scripts which enables the Menu to dynamically remove the options not found in the current compilation).
- Acronis Tools menu in the Boot Menu (includes : True Image, PartitionExpert, RecoveryExpert, DiskEditor and DriveCleanser).

911 Rescue Software (Drivers):
- New international options added (international keyboard layouts added, also an option to set the TimeZone in NTFSDOS Pro).
- USB Mass Storage support is added through the DUSE driver.
- Removed the EMM386 driver from the 911Start bootdisk (to enable Hitachi Drive Fitness Tests (DFT) to run again, and to remove the PowerQuest tools warning).

911 Rescue Software:
- Windows 2K/XP Setup assistant (Info are stored at design time, but can be further edited prior to installation).
- AMI Diag (finally a hardware diagnosis program).
- Active@ Kill Disk (a small safe erase utility).
- Reset CMOS info is added.
- Added an option to load NTFS Pro from the 911Menu.

- Can now load the NTFS support to the AntiVirus engines through the Alternate version of NTFSDOS Pro.
- The AntiVirus engines are now copied to the RAMDrive prior to running (for faster execution).
- The classic command line tool SWEEP is added to EPROMPT, also PERUSE is automatically loaded with DOSKey (press the SCROLL LOCK key to see it working).

CD Builder:
- Now uses MKISOFS v2.01a17 (to use the ISO9660:1996 filesystem and drop the Joliet extentions completely).
- Now the Bootdisks/bootsectors of Windows 2000/XP, Windows 98/Me, ERD Commander 2003 and O&O BlueCon XXL are created when actual Setup files are present on the CD (so that the Startup script detects them correctly).
- More Exception handling code (for more user friendly error messages).
- The rare error "Runtime Error 380" is now fixed.
- Hotfixes slipstreaming code is removed (the code was buggy from the beginning), if you need to slipstream hotfixes use WinCDMan to create a full slipstreamed CD and use it as your Windows Source CD.
- Can inject unattended Setup script (auto-generated if no one is supplied) in the Windows 2000/XP installation folder, for fully automated installations.
- The Windows 2000/XP Product Key window is not displayed if you selected not to enable the Win2K Setup Assistant.
- If DFL is run on the created CD Contents folder before creating the final ISO file, MKISOFS will optimize the CD contents so that duplicate files are written only once.

Disk Builder:
- New DOS files extraction method (Import_DOS.cmd is now integrated inside the built-in DOS extraction module).


If there is any missing feature that you would like to be included in the new release, you can post about it now (before the official release is out).

Best Regards to all.

Well i dunno if this feature is already in the current 911 builder but having this cud really be very helpful...

While starting the antivirus scanning, cud it be possible for u to actually ask the user for a path to be specified ?? that cud enable using the latest definations irrespective of how the cd actually is...

Well everything else seems PERFECT

Bye,
JAssi

OK, I have some sugestions:
- put somewhere in Builder option to include custom folder for every group in menu ( custom AV soft, custom partition recovery soft ...). This can be done just by puting a pointer to custom BAT file ( eventualy asking if that program needs NTFS support ).
- put an option to include custom CDShell menu script ( for a lot of IMG files not included in 911 CD )

That's because I have a 100MB more tools to add ( yes, I can add this alone, but someone don't know how )

Sorry for my English

@Jassi
Maybe I should do this option (its a good one).

@bobby100
1- The 911Menu is currently nearly saturated, so I can't find a free menu entry for the custom batch files (although it is a good idea).
2- The CDShell customizer would be a part of the v5.0 CD Builder (I was working in it the whole summer, then suddenly I started learning Delphi, and I thought that maybe re-writting it in Delphi would be a better idea than continuing with its VisualBasic code, so it wil be delayed for some time).
But I think the new CDShell scripts will make this step very easy (I should post a small tutorial about customizing my CDShell scripts in the website).

Chee thanks DOC !!

what about the unattent.txt file ive seen you guys talk about before. is there anyway to put in the cd builder the extra entries right there so you dont have to mess with the txt. say add the lines to execute the batch for the hotfixes or anything else you want to run on first boot.

Yes, I'd like to offer my services as a beta tester. Was doing a search on why the IBM DFT tools
weren't working properly on my CD (thought the EMM386 might be the culprit). So, sure...send that link
my way Doc...

c4

Doc,
I would love to test out the new version, please send me the link to the new version. By the way thanks for the help a while back with how to bypass the Out of memory problem I was getting.

-JAL-

New Version is highly recommended a true tribute to Doctor XP;

Windows 98 Second Edition
Windows XP Professional English (SP1a Slipstreamed)
All the Utilities except for ERD 2002/2003 (which is on a 2nd CD along with windows updates etc)

= 579MB Leaving 121MB Free Space this is truely a remarkable disk created by a remarkable guy and personally wish to say thank you.

TheWasp

@iN2Fun
The unattend.txt file is automatically generated by the 911 CD Builder, and is stored in the Windows NT Setup assistant, and (with a selectable option) can be stored in the I386 folder as WINNT.SIF.

But it doesn't include any lines regarding the programs to be executed at first run, you need to add it by hand (the CD Builder includes the ability to take a custom unattend.txt file).

@jloaiza
You didn't send me an e-mail with your e-mail address, please do if you still want to contribute in the beta testing.

@TheWasp

any news, when the beta test will be finished and everybody can lay his hands on the new and exiting cd builder version?

best regards,
highend

Hey, Doc:

Yo, sign me up for that link for the beta s/w. My email is:

mohawk1@juno.com

Thx!

Hello Doctor XP, i think it would be nice to have Bart's PE Builder CD included. Mybe instead of Erdcommander 2003 which is to expensive for most of the users. If it is possible a script should check if erdcommander or pebuilder is used.

Rgds
Wile Coyote

The CD Builder is capable of detecting the PE as an ERDC, so you can already use it instead of the expensive tool.

Check out my posting here (my second post in that thread) for a detailed howto, although the PE Builder section was geared toward adding just Nero.

CWP

I'd like to get in on this.

zero_cool_online@hotmail.com
Thanks!

If you want to sign up, you need to send an email to the Doc:


Just click on the "Email" link in the first post of this thread and send it. If you don't want to use the forum's interface to send the email, use doctor_xp@911cd.net.

CWP

CWP thank you for your fast reply and sorry i haven't seen your posting about that.

I have another problem. I'd like to have dos drivers for nforce2 and via onboard ethernet controllers included in the cdnetplus disk because many of my friends own such boards. But i don't have enough information to build the ndis.nic and the ndis.txt file. Does anyone have it ?

In order to have the network drivers for the nForce series, nVidia has to release DOS versions of the driver. Unfortunately, they don't have that in their agenda. As for the VIA NIC, there is a VIA Rhine driver (called FETND) that should either have came with the CD builder or in the extra NIC pack (more likely in here). Give it a try:

• Run the builder.
• At the first page, deselect "Accept default list of Network drivers".
• Continue until it asks you to select the drivers to be included. Scroll down to find FETND and put a checkmark in the appropriate box (it's sorted by the description column, so it'll be near the end).
• Everything else can remain the same.

CWP

Thanks again for your reply CWP. I found out that in most of the cases the ethernet controller on nforce2 motherboards is a realtek RTL8139C chip. I'm going to try the dos drivers for this chip.

Oh, you meant via... not VIA. Heh, yeah, I haven't found any motherboards with nForce and VIA Rhine together, only Realtek's. I think this driver is included by default, but it wouldn't hurt to look anyway .

CWP

@Preacher, Creater
You should receive your beta testing emails now, I ve send them.

@Wile Coyote
I intend to add the WinPE environment to the 911 CD, but I want to include it as a highly customized version (a special menu for the 911 Windows Utilities, and much more customizations) so I just need my time to publish a high quality menuing system for my applications.

And for the Realtek8139 drivers, they are in the default drivers list, so they are automatically included in the 911 CDNet Plus by default.

@CWP
Sorry for the mistake. I meant both driverpackages VIA and Realtek. I found both as Doctor xp said on the driverlist and have to test it asap.

@Doctor xp
Sounds great. In the meantime i'll try the posting of CWP to add it.

Rgds