kof94

I think you misunderstood me. The default menu for Ubuntu uses something called gfx which isn't the same as vesamenu. You don't need the original isolinux folder from the Ubuntu disc just the isolinux.cfg file. Open it up with your favorite text editor and copy the relevant commands to your menu. If you require extra options like languages you'll need to add them to your menu as well. You can find the extra options in the F*.txt files (* representing an F key number).

If you actually check out benners script you'll realise it does use silent switches to install. I imagine the main reason you'd want a script like this is so your not breaking the freeware license by distributing the installer! It would be a bit extravagant to create it just so you could have the latest ver, although I could be wrong .

I can tell you one thing, I never managed to get Win9x to boot exactly like the original disc i.e. with auto-fdisk and format. To be honest it's been a while since I messed with UA Win98 so I'm probably not the best person to ask anyway. Take a trip over to the Win9x forum and see what you can pick up, that's what I did. Soporific has some very good UA guides and projects that you might want to check out. Here's two threads in particular: The Unattended Boot CD for Windows 98/98se Windows 98 Seven Years Later Edition Boot CD Good luck

If you've copied the folders I specified to the root of your disc structure you can use the default boot commands from original Ubuntu isolinux.cfg. The kernel and initrd are in the 'casper' folder and not the usual isolinux folder so no editing is required!

Flyakite's guide only shows you how to execute setup.exe using a win98 boot disc, you still need to partition your hdd first. Your best bet is to add a menu option in config.sys in your boot image. One to run setup and another to drop you to the command prompt so you can partition your disc. -kof94

I think we have different goals here. I could get by without the live CD part since I have Ubuntu installed as my secondary (although fastly becoming more primary by the week) OS. I have to agree though that the live CD is rather weak. I solved the issues with k3b and taken a proper look at it, it's quite an app . I'm might start using it since you can now access NTFS partitions from Ubuntu. As you can tell I'm testing out a Windows XP=>Ubuntu migration. Might as well since Vista doesn't exactly inspire me!

Ubuntu works A-OK from my project. Although I do use the default locations and boot commands but that doesn't bother me, I'm past caring about having everything in one folder and I'd never install one of the other buntu's anyway. Thanks.

Sorry Jet, I completely overlooked it in the first post. I don't know why, I know I've read the whole thing a number of times. I was under the impression though that certain Distro's needed Joliet e.g Knoppix. I know I needed to add this setting to my previous images using CDShell to get version 4.x of Knoppix to boot. I don't really know why I want to get away from CDImage, it does the job I want it to do after all. I suppose it's just the whole M$ thing. With the amount of testing and p***ing about I do when creating my discs I'd be in and out of Slax every five minutes if I did that. On the other hand, if I could get k3b to work properly in Ubuntu it wouldn't be so bad. Not a bad idea. Put it this way, I've got a bloody great big hole in the wall next to me with a cable going through it .

I would love to use mkisofs instead of CDImage but no one will tell me of a decent set of switches that will keep Windows and Linux happy. I also require file optimisation (writing duplicate files once) because I have two vers of XP on my disc. Where did you get your mkisofs GUI from? Moving on, Kubuntu, Ubuntu and any other buntu will probably give you a head ache. I personally prefer Ubuntu, the folders required are: .disk boot casper dists pool preseed The rest are just there for the Windows apps! In previous versions you didn't need the .disk folder but as of Feisty Fawn you need it. Must be a tag or something i.e. with out it the live setup cannot find the .squashfs file.

I can't say I've ever seen a usb key detected as a fdd, only 'removable storage'/hdd. Saying that, there's no reason why it couldn't be, so it's a valid point.

Probably not since A: and B: are usually reserved for floppy drives. If you are booting to a PE you could probably hard code it to either of these though.

I'm sorry but I'm lost with this, I've never encountered such a problem. It's kind of weird that it should complain about the cls command but saying that it is the first command in the script. Are you sure you haven't corrupted cdsh.bin with your hex editing antics? My suggestion would be to start over (yet again) leaving everything where it should be, in the /boot folder. One step at a time!!!

The boot sector for UBCD in Flyakites guide is in fact loader.bin from the CDShell package!

The boot.bin file is a generic xp boot sector and yes you need to point CDImage to your loader.bin instead. The only file you should have needed to hex is loader.bin to change the boot location from '/boot' to '/cdsh'.

Thats normal ignore it unless you get hundreds of them. It usually happens to files like setupldr.bin after you've hexed it.

Thanks, I wasn't 100% sure about this. It's also nice to know there's a workaround, although I personally wont be using Vista for some time. Edit: It probably would have helped if I'd read the third post in the thread as well .

Ok, so you have a carbon copy of Flyakite's cdshell.ini. 1. First thing you need to is to break it down a little. Make yourself a simple menu with some sample options. Debug that menu until you've got it right, then use it to create sub-menus. This a mod from one of my previous incarnations: cls print "\n" print "Press any key to boot from DVD...\n" getkey 5 boot 0x80 main: set textColor = color[cyan on black] cls print l "\n" print l " ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»\n" print l " º System Recovery DVD º\n" print l " º Version n/a º\n" print l " ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ\n" print l "\n" print l "\n" print l " Main Menu\n" print l "\n" set textColor = color[brightgrey on black] print l "\n" print l " [F1] Windows XP SP2\n" print l " [F2] UBCD4Win 3.03\n" print l " [F3] Ubuntu 6.10\n" print l " [F4] Knoppix 5.1.1\n" print l " [F5] Ultimate Boot CD 3.4\n" print l "\n" print l " [F6] Utilities\n" print l "\n" print l " [ESC] Exit\n" getkey if $lastKey == key[f1]; if $lastKey == key[f2]; if $lastKey == key[f3]; if $lastKey == key[f4]; if $lastKey == key[f5]; if $lastKey == key[f6]; if $lastKey == key[esc]; then reboot if $lastKey == key[end]; then goto prompt goto main prompt: cd / cls end It's simple but should aid you a little since there's no functions or variables in it. 2. Re-download the CDShell package since your problems could be due to corruption or missing files (it's worth ago!). 3. Get yourself a copy of CDImage GUI. It comes pre-set with the most reliable settings but here are mine anyway: cdimage.exe" -l"AIO" -h -j1 -b"E:\Disc\isolinux\isolinux.bin" -x -o -m "E:\Disc" "E:\Disc.iso" This way you should be able to rule out any misuse of CDImage (been there, done that!). 4. cdshw.com is buggy as hell, don't trust it explicitly. Examples are: It doesn't like you having Caps-Lock on and you cannot exceed 10kb (or somthing like that I can't remember) on any config file e.g chshell.ini. There are other things that will randomly crash it as well. You just can't beat a real test (this is also true of VPC)! 5. I never tried booting Vista from CDShell although I cannot see it being significantly different from other NT family OS's to not work. The main issue here is CDImage. As far as I know Vista installation files come packed in a single archive similar to a Linux squashfs file (correct me if I'm wrong). I cannot see CDImage optimising two of these archives if their make up is significantly different. The reason it works for XP/2K/NT etc is because each individual installation file is bare to see on your disc. So, the files for say, XP Home and Pro will be optimised to a certain extent because most of their files are identical! With Vista, if my assumptions are correct, this just isn't going to happen! Last of all, there's always isolinux. Just a thought . Good luck.

Do yourself a favor and grab yourself a copy of Notepad++, makes life a lot easier! Post your script and we'll try to debug it for you. CDShell is right pain when you can't find a bug in your script and it only takes one typo to screw the whole thing up.

That is going on my list of reg tweaks. If I'd known that in the past it could of saved a lot of time. Thanks

You could just use UltraISO or a similar app to get the boot sector from your own media. The file your referring to is way out of date anyway.

I have to agree that's gotta be painful . Incidentally, you probably broke the check sum because you saved your modified file with the wrong encoding. If you don't know what I'm talking about, when you go to 'Save As' you will see the drop-down box for encoding!

This explains it all! You cannot run the Microsoft Software Installer service in safe mode i.e if your prog used a .msi installer you won't be able to uninstall it in safe mode. My suggestion would be to run msconfig in safe mode as Admin, disable anything and everything that could affect the system booting (e.g. PC-cillion) then have another crack at a semi-normal boot. If that doesn't work then I'd suggest a repair install from your Windows XP disc. This will basically check that everything is were it should be for normal operation without you having to resort to a full reinstall. I know this is all basic stuff but it's always a good idea to go for the easy fixes first. Obviously this could be a factor as well . -kof94 P.S. Have you tired running 'Last known good configuration'? Just another quick fix thats worth a crack!

^^ See first post

One suggestion. After performing any kind of integration it is good practice to create a new boot dir from it. This way you rule out any errors. This particularly important if you integrate text mode mass storage drivers.

The reason Ryan was asking weather you guys were using his update pack is because plugin.ocx is removed during intergration. I believe this is because one of the IE hotfixes removes it as well. It is normal behavior to see an error in the setuperr.log regarding this issue. It is rather puzzling, however, that setup fails to continue because of it. My suggestion would be to start over with a fresh source since it looks like you have a bodged integration. Good luck.