Was looking for a disk partitioning free ware... Mis-read the WinUBCD forum... thought one was included.

Any suggestions where I can find one?

(Love the CD anyway.... Will help a bunch with other projects...)

Kenny

Most operating systems have partitioning programs. What are you trying to do?

Ranish v2.40 or 2.44 is my favorite 3rd party partitioning tool. XOSL is a great boot manager at the same site:

http://ranish.com/

With v2.44 you can create up to 32 primary partitions on a drive. Each one can be bootable; XOSL works as a great boot manager.


MS: DiskPart

http://www.microsoft.com/resources/documen...s_diskpart.mspx

http://www.serverwatch.com/tutorials/artic...10825_1467381_3

Good luck! Everytime I partition and install I wish that I'd done the partitioning differently for one reason or another.

You should be able to adjust your partitions with the MMC tools included in the project.

Click "UBCD4Win"--->Programs---->Administrative tools

Digital Dolly is a free tool that will resize partitions for you.

The ubcd4win only has destructive ways of resizing partitions, but can create them on a raw drive.

I built the stock 2.55 ubcdwin cd and i get an error message that the RPC server is unavailible when I try to run the MMC module.

Also when I try to run the DiskPart software , [start][system][storage][diskpart] it flashes a dos shell and then the shell dies before I can read what it is saying...



maybe my cd wasn't so stock after all?

I sure could use a disk partitioner on here, any clue what's going on here?

j

In the PC Pro mag Sept 2005 Edition there's a copy of Paragon Partition Manager Personal Edition.

Order here

Paragon Plugin here

I'm really not sure what is going on. Did you add anything to your project files before creating the ISO? Did you follow the instructions? Those tools should run, I haven't had any problems with them.

just the 1.6 drivers.

I didn't see any errors and everything else seems to run. Well if it's me I can start over from scratch and be more alert.

speaking of which are the 1.6 or 2.0 drivers the way to go these days? last time I checked the 1.6 drivers had the most recent creation date.

Thanks!

j

The newest version is 2.01, however 1.6 may have a newer date because it was initially removed from many mirrors after 2.0 was released. But then people started requesting the old version and a few mirrors have put that version back up.

Installing the drivers the "old" way is much easier. Just execute the EXE file and direct it to your "C:\pebuilder313\drivers" folder and they are added. The new version includes many more drivers but requires more work. Please view the instructions post for 2.01 here:
http://www.ubcd4win.com/forum/index.php?showtopic=3208

Read it over and then decide which method you would rather attempt. It's up to you. Good luck, I don't know if adding the drivers will help your specific problem. But I hope that you get these programs working.

@Ben and everyone...
Should I try to update the old drivers some more again? There are so many requests anymore... I don't know... :-\

I was going to try to talk to you about that last night when I called you on the phone. I have heard from several people that they like the old way and would like to see it continued. I personally feel that I think we should keep BOTH methods and I've been thinking that we could rename 2.01 to BTSDrivers1.0 and then continue on with updating 1.6 to 1.7 and so on. I know you are really busy with trying to find a new job and with everything going on it's probably hard to concentrate sometimes. So what do you think about this idea??

Well, I was thinking more of doing something like 1.6.01 and incrementing slowly... but your idea sounds a bit better... The only thing is that the old drivers aren't that great when it comes to Storage adapters, but they seem to work really well with NICs... so to me, having both is the best idea too. Now I just gotta go and update all of the current drivers and hopefully find all of the posts with new driver additions... :-\

Yes I think the bts packs are best for storage drivers and should continue that way but for lan I think it appears as though the old way is better. I also think it would be best to use a combination of the two.

And since autobuild will be a part of the next ubcd4win then i think it would be easy enough to include the bts drivers as part of the default. or at least the mass sotrage part. The rest will need some more work and re-evaulation. I think that this method can work well but that the way that bts distributes them is not optimal.

I actually like the CPU and Chipset drivers as well from BTS, so I think including those with his MassStorage ones would be great, and just include the Network ones from mine. Though, we'll still keep the options of going only with the BTS ones or only with mine, either way, it should help.