.. also resultant iso larger than what I started with
... yes, the compression isn't optimized but quick.
You don't need to burn a CD (or DVD) each time; select your new created ISO as boot device in VirtualBox. If the ISO runs well in the VirtualBox enviroment you can burn it in a few days and it will work.
... yes, of course, 'quick' is relative. You have VirtualBox installed in Windows 7 - and Windows 7 is a very lame OS, which does not leave enough CPU power for applications like VirtualBox.
The last version of VirtualBox is 4.0.10. For USB-support you need the extension pack. To read the manual use [F1].
For each virtual machine you want to run in VirtualBox you can do many decisions. For example 'System > Processor > 2 CPUs and many other things.
For each virtual machine you want to run in VirtualBox you can do many decisions. For example 'System > Processor > 2 CPUs and many other things.
Specifically can't find this cpu choice now.
All my current problems are VirtualBox problems it seems.
Werner has taken care of all the re-mastering details.
Initially, I told VirtualBox the guest would be linux/Debian, that's all.
only one cpu recognized.
guest x11 resolution not right, even tho' CD had it ok.
...note: virtualbox-guest-x11 isn't installed and won't.
can't read auxiliary fat32-formatted data USB from guest apps.
don't know how to export final iso to host, and
...don't know how to get current iso into iso9660 format.
not sure whether current guest image is what will appear
...as the /remaster/iso.
Can't locate earlier snapshots, only the last one.
Did you set the number of processors for your virtual machine?
Hi, Klaus
For the life of me, I can't find the gui you mention.
When I did answer the question, it only took 'one' for an answer,
for a reason having to do with some missing interface programming.
Is this qui available after the initial question phase has been passed?
An update: using a cheatcode on the kernel default line to remedy 1366x768 problem. Biggest immediate problem is how to bring in text from an auxiliary usb.
Can't figure out the 'shared folder' secret.
I gather what's going on here is that what's been created is a virtual hard drive install of Debian.
Is that the big idea behind re-mastering?
All my current problems are VirtualBox problems it seems.
I wonder this feedback is typical or not. If we think this is typical, then perhaps doing the remastering in VirtualBox is not so good an idea. Instead of completing the task of remastering, one ends himself up in learning how to use virtualbox.
Some time ago I proposed a remastering using a typical poor-man install. Of course, as usual, I am not a very patient guy, I never carry the idea all the way through but I ***THOUGHT*** Forester later came out with a script which make it even more friendly. He published the script somewhere. Though I haven't use it but I think remastering using this method is a better approach. I don't like the 'chroot' method because I think in a typical 'chroot', the final system behaviour is only tested during the few hours of 'chroot' - which is often inadequate to represent the final thing the user want to see and there maybe some "side-effects" which were not noticed during the few hours of usage. Whereas using 'poor-man' install, what you see is what you get. There is no urgency to remaster if you think it is not yet proven stable. You can remaster after 3 months of usage if you like.
You have to install GuestAdditions. Please read in VirtualBox manual> 4.2.1. Guest Additions for Windows
don't know how to export final iso to host,
First of all you have to copy the new ISO to the directory of isoimages from VirtualBox. Don't know how this looks like beneath Windows7 and how you can do it. Perhaps you need an USB-stick to make the copy from VirtualBox to the directory in Windows. With Linux it is all very easy to do
After this you can mount the new ISO in VirtualBox to start from it.
My description is for experienced users; users who never worked with VirtualBox have problems. VirtualBox isn't a tool you can learn within a few minutes.
I don't like the 'chroot' method because I think in a typical 'chroot', the final system behaviour is only tested during the few hours of 'chroot' - which is often inadequate to represent the final thing the user want to see and there maybe some "side-effects" which were not noticed during the few hours of usage
With my method of remastering in a virtual drive enviroment you can create new ISOs over and over and test them with VirtualBox without the necessity to reboot always your conputer.
Or you install the remastered new ISO to an USB-Stick and make extensive tests with it in the Virutalbox. And so you have the ability to eliminate all "side-effects" or integrate new features.