[EldRick]

I'm a complete newbie, but having installed one 10v successfully (after some goofs), I'd suggest two improvements to NetbookMaker:

- Insert a few lines of code so it will not install to the current boot drive. This could avoid some seriously fried Macs.

- Rename it to something less easily confused with NetbookInstaller, like maybe NetbookUSBbootMaker. This would avoid quite a bit of confusion as to the purpose and functions of the program.

Great job though - the degree to which the 10v works well is amazing - a lot of hard work that is appreciated...

[outphase]

Originally Posted by EldRick

- Rename it to something less easily confused with NetbookInstaller, like maybe NetbookUSBbootMaker. This would avoid quite a bit of confusion as to the purpose and functions of the program

NetbookBootMaker is already a companion to NetbookInstaller. How would NetbookUSBbootMaker be any less confusing than NetbookBootMaker?

[atm153]

I agree with both statements, but I'd recommend something more along the lines of Netbook USB Boot Tool (with the spaces) otherwise it looks way too long.

Great to see a new member getting involved in the community!

[bmcclure937]

I partially agree with the first statement and do not agree with the second.

My thoughts are that you should only be doing these things if you really know what you are doing. Thus, you should be able to differentiate between the target USB volume you want to patch with NBM and the system volume. I guess it would not hurt to make it more "idiot proof" and not allow patching of the system volume. Also, any guide you follow will specifically tell you to select your correct volume.

The second item I do not agree with at all. As outphase mentioned, NetbookBootMaker is an adequate name and the application belongs to a family of application (the NetbookInstaller "suite"). Making the name longer would make it more confusing. And explain to be how NetbookBootMaker is not descriptive enough (while still being short). Saying NetbookInstaller and NetbookBootMaker is natural now.

Just my $0.02

[meklort]

There are reasons why you'd want to install NBM on your internal drive, I could make a warning if it detects you are trying to do so, but I wouldn't disable it altogether.

[Bear Hunter]

Originally Posted by EldRick

- Insert a few lines of code so it will not install to the current boot drive. This could avoid some seriously fried Macs.

Not sure I understand this statement. How does this fry your Mac? For example, i routinely use the method where you connect your mini HD to the Mac for the OS install. The last step is running NBM and shutting down. If your booted into the mini HD and run NBM it does nothing to the MAC.

I think what you really mean to say is disabling the host computers HD (the MAC) as an option in the drop down menu. Let me expand a little bit on this. Lets say when you format the mini HD and name the partition "Macintosh HD"...there would be no way to tell which HD is the mini and which HD belongs to the MAC. If you accidentally chose your MAC HD...then yes that = trouble. This is why I always name the HD for the mini "Mini HD".

Is that about right?

EDIT:

After thinking about it some more, I'm not sure you could disable host HD as an option in the drop down menu in this instance. Maybe the warning is the way to go. Something like, make sure your installing NBM to the correct drive or something.

[mechdrew]

According to my 10v, it is a Mac, so disabling the boot volume in either software is a bad idea. Warning is a good idea for BootMaker (in the case of a real Mac), but not for Installer. Anyone who uses NetbookInstaller has already been warned via a yellow strip message. I could also see one scenario where a person would want to run BootMaker on the boot volume on a netbook.

Name change is also bad. It just complicates it more, and we've already been through two name changes for this type of software. NetbookBootMaker does exactly what it says, make a bootloader for a netbook. Same logic for NetbookInstaller, it's supposed to be installed only on a netbook.

[yidakee]

Just an underscore between terms would make all the visual difference in the world!

After you are properly familiarized with it, there is no possible confusion. But by that time, you've managed to install anyways... The thing is, the term put together look graphically very simillar.

Boot book bookbootboootbook bootloader installer ... thats basically it. And the brain has a little more trouble here with quadruple "o"'s , plus due to them having "net" to start and "er" as ending, it has to try to decode the middle and then bookboot gets in the way. Its all saved by a single _

Netbook_BootMaker
Netbook_Installer

yeah, I study Psychology and Consciousness Research... so... my semi-scientific 0.2c

[ian]

Originally Posted by yidakee

Just an underscore between terms would make all the visual difference in the world!

After you are properly familiarized with it, there is no possible confusion. But by that time, you've managed to install anyways... The thing is, the term put together look graphically very simillar.

Boot book bookbootboootbook bootloader installer ... thats basically it. And the brain has a little more trouble here with quadruple "o"'s , plus due to them having "net" to start and "er" as ending, it has to try to decode the middle and then bookboot gets in the way. Its all saved by a single _

Netbook_BootMaker
Netbook_Installer

yeah, I study Psychology and Consciousness Research... so... my semi-scientific 0.2c

Personally, I think something should either use camelCase or underscores and not mix the two. So, I wouldn't want to see the introduction of underscores in this way.

[grassle]

Originally Posted by ian

Personally, I think something should either use camelCase or underscores and not mix the two. So, I wouldn't want to see the introduction of underscores in this way.

Well, we're entering tast/style land and there exists no arguing...
I prefer to see underscores and CamelCase as two differently strong ways to separate semantic chunks. In this view,
Netbook_BootMaker and Netbook_Installer have some charm in that the stronger division by underscore separates the function chunk, which is again subdivided with the weaker camelcase for BootMaker.

g.