It is currently Wed Nov 26, 2014 10:39 pm

All times are UTC - 8 hours




Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 28 posts ]  Go to page Previous  1, 2
Author Message
 Post subject:
PostPosted: Sat Dec 08, 2007 4:44 am 
Offline

Joined: Mon Feb 21, 2005 10:59 pm
Posts: 1305
OK, I understand your suggestion now. Will try to work this into the next release too.

My only worry is that some apps might not be able to run from RAM disk, so I will have to leave those out, if I find any.

If memory serves me right, Avast had some problems running from RAM disk (though we have taken that out of UBCD).


Top
 Profile  
 
 Post subject:
PostPosted: Sat Dec 15, 2007 5:10 pm 
Offline

Joined: Thu Dec 21, 2006 4:28 pm
Posts: 85
@Victor

OK, here's the beginnings of my 'extract to ram' idea.

* Edit autorun3.bat on fdubcd to include this:

Code:
set path=%path%;%ramdrv%\apps


I did this so that when you launch apps from /dosapps you stay in that location when you've finished.

* Download enufdisc and stow from here (they have personal licenses so should be fine for UBCD) and add them to /bin on the fdubcd.img.

* Create a batch file called runapp.bat with the following contents and add it to /bin in fdubcd.

Code:
@if "%debug%"=="" echo off

set n=
enufdisc %ramdrv% 5000000 | stow n > nul
if "%n%"=="1" goto setup
if not exist %ramdrv%\etc\ramdrv.txt goto setup
call w.bat box @%ramdrv%\etc\ramdrv.txt:ramdrv #1,25
if errorlevel 100 goto setup
if errorlevel 2 goto setup
if errorlevel 1 deltree /y %ramdrv%\apps\*.* > nul

:setup
if not exist %ramdrv%\apps\nul mkdir %ramdrv%\apps
if not exist %ubcddrv%\dosapps\%1\%1.zip goto end
unzip -o %ubcddrv%\dosapps\%1\%1.zip -d %ramdrv%\apps > nul

:end
set n=
set ?=
set wbat=


This will be used to check available space on the ram drive and extract the app to it.

* Create a text file called ramdrv.txt with the following contents and add it to /etc in fdubcd.

Code:
:ramdrv "Low RAM Drive Space!" [x]
                 (~press any key~: #? sec.)

  Cleanup ~%ramdrv%\APPS~ to create more space?

               [Yes] [?No]

::


Message for runapp.bat!

* Finally create zip files of each app's files naming them after each app (see runapp.bat) then modify startup.bat to use runapp.bat. Here's and example for SCSIMAX:

Code:
@echo off
cls

echo Loading...

call runapp scsimax
if not exist %ramdrv%\apps\scsimax.exe goto err
scsimax.exe
goto end

:err
echo.
echo ERROR!!!
echo.

:end


I've stolen some idea's from another well known project here (uhm) aswell as adding a few of my own... what you think?

Edit (17/12/07): Simplified runapp.bat, lowered 'low ram drive space' threshold and moved error checking to startup.bat
Edit (22/12/07): Changed dir on ram drive to %tmp% to simplify things abit
Edit (22/12/07): Reverted dir on ram drive to %ramdrv%\apps due to problems with cleanup (vcswap000)


Last edited by kof94 on Sat Dec 22, 2007 2:38 pm, edited 4 times in total.

Top
 Profile  
 
 Post subject:
PostPosted: Sun Dec 16, 2007 3:24 pm 
Offline

Joined: Thu Dec 21, 2006 4:28 pm
Posts: 85
More stuff for you.

As I understand it XMSDSK (the ram drive for fdubcd) can only address up to 2gb of ram, any more and it fails.

Considering that you can now buy a system on high street with 4gb of ram I thought it might be a good idea to add a back up ram drive for fdubcd.

I added shsurdrv.exe to the image (which I believe doesn't have the same issues as xmsdsk, correct me if i'm wrong) and edited autoexec.bat (at line 137) to read like this:

Code:
echo AUTOEXEC: Setting up Ramdisk at drive %ramdrv%
if not exist %srcdrv%\bin\xmsdsk.exe goto _shsurdrv
xmsdsk %ramsz% %ramdrv% /y /t
if errorlevel 1 goto _ramok
:_shsurdrv
if not exist %srcdrv%\bin\shsurdrv.exe goto _abort
shsurdrv /D:%ramsz%K,%ramdrv% /T /QQ
if errorlevel 1 if not errorlevel 255 goto _ramok
goto _abort


Instead of this:

Code:
if exist %srcdrv%\bin\xmsdsk.exe goto _xmsdsk
if exist %srcdrv%\bin\shsurdrv.exe goto _shsurdrv
evnwrdrv %ramsz%%ramdrv%
if errorlevel 1 if not errorlevel 255 goto _abort
if not exist %ramdrv%\nul goto _abort
goto _ramok
:_shsurdrv
shsurdrv /D:%ramsz%K,%ramdrv% /T /QQ
if errorlevel 1 if not errorlevel 255 goto _ramok
goto _abort
:_xmsdsk
xmsdsk %ramsz% %ramdrv% /y /t
if errorlevel 1 goto _ramok
goto _abort


I have no idea what evnwrdrv is like as a ram drive to I wrote it out all together!

Again what do you think? Incidentally is Erwin still actively developing NwDsk?

-kof94


Top
 Profile  
 
 Post subject:
PostPosted: Mon Dec 24, 2007 6:07 pm 
Offline

Joined: Mon Feb 21, 2005 10:59 pm
Posts: 1305
I chose the lazy option. I simply deleted xmsdsk.exe and added shsufdrv.exe, since the disk image didn't have room for both anyway. So shsufdrv.exe is automatically used on boot up. Do you think that's OK?

Also, wanna confirm, is the latest version of shsufdrv.exe available here?

Quote:
Incidentally is Erwin still actively developing NwDsk?


Erwin seemed to have dropped of the radar since early this year. All my emails to him went unanswered, and his website has not been updated for a while.


Top
 Profile  
 
 Post subject:
PostPosted: Tue Dec 25, 2007 3:20 am 
Offline

Joined: Thu Dec 21, 2006 4:28 pm
Posts: 85
Victor Chew wrote:
I chose the lazy option. I simply deleted xmsdsk.exe and added shsufdrv.exe, since the disk image didn't have room for both anyway. So shsufdrv.exe is automatically used on boot up. Do you think that's OK?

Also, wanna confirm, is the latest version of shsufdrv.exe available here?


I was using a radically slimmed down (UBCD) NwDsk of my own design (I don't need network support) and just edited my scripts for the purpose of UBCD so I didn't think about the space requirements for the full image (oops). I'll probably ditch my idea though if your considering adopting this stuff.

As far as I know the version of shsurdrv on that site is the current version. Incidentally, previous versions of the (UBCD) NwDsk images used shsurdrv. As far as I've read xmsdsk is supposed to be the superior ram drive though, thats why I made the edit to autoexec.bat but I can't see any issues with just using shsurdrv.

Victor Chew wrote:
Erwin seemed to have dropped of the radar since early this year. All my emails to him went unanswered, and his website has not been updated for a while.


Oh well, it would have been nice to have had him make these changes and possibly expand on them, I'm no DOS guru after all.

The reason behind these edits is due to some of the idea's used in Hiren's boot disc.

Don't flame me straight away, I have no interest in warez and I have no intention of using the version I downloaded for productive means. I'm more interested in his use of DOS and the ram drive and how some of these ideas could be ported to UBCD. My 'extract to ram' idea is an example.

I still think UBCD has the edge and is vastly more expandable but it doesn't hurt to recycle a few ideas here and there 8).

What do you think?


Top
 Profile  
 
 Post subject:
PostPosted: Sun Dec 30, 2007 10:03 pm 
Offline

Joined: Mon Feb 21, 2005 10:59 pm
Posts: 1305
Quote:
What do you think?


Let's try shsurdrv and see how it goes... unless someone has any technical opinion to contribute over which one is better.

I tried researching on shsurdrv vs xmsdsk, but the result is inconclusive.


Top
 Profile  
 
 Post subject:
PostPosted: Sat Jan 26, 2008 4:14 pm 
Offline

Joined: Thu Dec 21, 2006 4:28 pm
Posts: 85
Few more requests.

For DBAN and NT Password and Reg Editor would you consider adding a submenu for trouble shooting options?

Examples:

Code:
LABEL ntpwd
MENU LABEL Offline NT Password & Registry Editor 070927 (default)
KERNEL /boot/ntpwd/vmlinuz
APPEND rw vga=1 init=/linuxrc initrd=/boot/ntpwd/initrd.cgz,/boot/ntpwd/scsi.cgz

LABEL nousb
MENU LABEL Skip Loading USB devices
KERNEL /boot/ntpwd/vmlinuz
APPEND rw vga=1 init=/linuxrc initrd=/boot/ntpwd/initrd.cgz,/boot/ntpwd/scsi.cgz nousb

LABEL nodrivers
MENU LABEL Skip Loading SCSI devices
KERNEL /boot/ntpwd/vmlinuz
APPEND rw vga=1 init=/linuxrc initrd=/boot/ntpwd/initrd.cgz,/boot/ntpwd/scsi.cgz nodrivers

LABEL irqpoll
MENU LABEL IRQ Error Fix (some devices)
KERNEL /boot/ntpwd/vmlinuz
APPEND rw vga=1 init=/linuxrc initrd=/boot/ntpwd/initrd.cgz,/boot/ntpwd/scsi.cgz irqpoll



Code:
LABEL dban
MENU LABEL Darik's Boot and Nuke 1.0.7 (default)
KERNEL /boot/dban/kernel.bzi
APPEND initrd=/boot/dban/initrd.gz root=/dev/ram0 init=/rc nuke="dwipe --method prng --rounds 8" silent

LABEL failsafe
MENU LABEL Failsafe Mode
KERNEL /boot/dban/kernel.bzi
APPEND initrd=/boot/dban/initrd.gz root=/dev/ram0 init=/rc nuke="dwipe --method prng --rounds 8 --verify off" floppy=0,16,cmos


For DBAN I've consolidated all trouble shooting options into one (Failsafe Mode). I've also preset the highest security wipe but that's up to you.


Top
 Profile  
 
 Post subject:
PostPosted: Wed Jan 30, 2008 9:23 pm 
Offline

Joined: Mon Feb 21, 2005 10:59 pm
Posts: 1305
Quote:
For DBAN and NT Password and Reg Editor would you consider adding a submenu for trouble shooting options?


Duely noted! Thanks for the suggestion.


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 28 posts ]  Go to page Previous  1, 2

All times are UTC - 8 hours


Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  

Protected by Anti-Spam ACP Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group