Print

[reddwarffan]

I was curious to see what actually worked in TinyCore so I fired it up again.  Again, I was unable to lock and unlock (the same error message from my previous post appeared in both scenarios) so I went tried something different and ran Option 2 to activate xboxhdm, which failed surprisingly due to shared library problem?  I figured it had something to do with my previous installation of either emelfm or Beaver so I downloaded a 'clean' build from sourceforge with updated ltools.tce.

Booted the clean version but still had problems with locking and unlocking, however, Option 2 worked all the way to the orignal xboxhdm screen but then an error message "Bummer, could not run /sbin/getty/" rolled continuously up the screen.  

Hope this update helps.

Couple of points for clarification:

1) I ran xboxhd3 instead of xboxhdm3 (as written up in my previous post)
2) Adding 'silent' to the grub loader command removes all the kernal info flash up at start up, looks cleaner!

[ldotsfan]

Fixed the problems with hdtool invalid option. The getty problem was solved in my version some time back but I've neglected to update the copy in sourceforge. It should be ltools.tcz to go to the tce/optional folder and initrd.gz to go to the hdmboot folder.

Please download and try them out. The qemu shared library problem is new to me. Perhaps you should grab qemu.tcz again? Off the back of my head, it is dependant on SDL, cyrus-SASL, libasound.

[ldotsfan]

It sounds like there's a mixture of xboxhdm2(the older alpha version??) and xboxhdm3 files on your usb stick?  For linux.iso to reappear I'm confused too.

CODE

Inappropriate ioctl for this device

I have seen this error before. It means that the new hdtool code for hdd locking/unlocking meant for SATA hdd isn't working. May want to go back to the old locking method used in xboxhdm2.1/2.2.

I want your honest opinion on TinyCore. If it is too much trouble for the average user of xboxhdm and has weird problems, I'm inclined to leave it aside and go back to SLAX.

Seems that we have to be less ambitious and scale back on the goals of xboxhdm3 then.

[ldotsfan]

QUOTE(reddwarffan @ May 23 2010, 04:24 AM)

I suppose the decision falls to you to go back to Slax, as you are the sole programnmer on TC.  It might be case of why fix it if it's not broken?  You have to ask yourself why pursue - it may use less memory and its faster, but is there a demand?  If you feel that we have hit the wall with TC then I am happy to continue to use Slax as my preferred method for building a xbox drive.  For me, the major drawback with Slax is the boot up time with a locked drive (about 7 mins).  I like the idea of TC - it's smaller, faster and boots up in 15secs even with a locked hd.  IF you got TC working then I would always use TC, that's why I am keen to see it developed.
Good point .  When I read xboxhdm3 was alpha I thought happy days -    - a few days of testing here and there to make it a generic solution but 9 days later I am hinking it should be renamed 'beta'.  

I am curious has anyone else had success with xboxhdm3, even yourself?

Hope this helps  

Thanks for your feedback. By the way, quoting from Wikipedia,

CODE

Alpha

The alpha phase of the release life cycle is the first phase to begin Software testing. In this phase, developers generally test the software using white box techniques. It is also known as Private beta. Additional validation is then performed using black box or gray box techniques, by another testing team. Moving to black box testing inside the organization is known as alpha release.

Alpha software can be unstable and could cause crashes or data loss.

The alpha phase usually ends with a feature freeze, indicating that no more features will be added to the software. At this time, the software is said to be feature complete.

"Beta" is the software development phase following alpha, named after the Greek letter beta. It generally begins when the software is feature complete. The focus of beta testing is reducing impacts to users, often incorporating usability testing. The process of delivering a beta version to the users is called beta release.

The users of a beta version are called beta testers. They are usually customers or prospective customers of the organization that develops the software, willing to test the software for free or for a reduced price.

Beta version software is likely to be useful for internal demonstrations and previews to select customers. Some developers refer to this stage as a preview, a prototype, a technical preview (TP) or as an early access.

I will put the project on hold until I sort out the SLAX/TC design considerations. Thanks for your testing efforts so far.

[liteon6x]

hello guys i have been using xboxhdm2.2 i have a a problem

i drag all the files from my xboxhd 1.9 disc that i normall use to build hdds then put them on my sd card that the programs format (yes i use that instead of a thumb drive) every thing goes fine, i build the xbox and all but when its done the file name are Truncated for example xbox media center will be xboxmed~1 and so on

i reverfierd the files i got off the cd and there are the correct names so when its doing it thing in linux it is happening

what can i do

[ldotsfan]

QUOTE(ldotsfan @ May 23 2010, 08:34 PM)

I will put the project on hold until I sort out the SLAX/TC design considerations. Thanks for your testing efforts so far.

I decided to throw the TinyCore/new hdd locking changes away and scaled back on the changes. Started from xboxhdm2.2 as baseline and added an addon pack for xboxhdm3. The command is xboxhd3 for the new stuff:
1. 32k/64k FATX.
2. Large partition support (xbpartitioner-like) for F/G.
3. Displays the HDD model no besides the device name to ease identification of the hdd device.

Unzip the file to the usb flash drive to try it out.

xboxhd2 is still there for compatibility. The hdd locking retains xboxhdm2's functionality. I've used RMPrepUSB instead of Bootable USB-Drive Utility due to recent reports of issues.

[nugmebot]

QUOTE(ldotsfan @ Jun 15 2010, 02:38 AM)

I decided to throw the TinyCore/new hdd locking changes away and scaled back on the changes. Started from xboxhdm2.2 as baseline and added an addon pack for xboxhdm3. The command is xboxhd3 for the new stuff:
1. 32k/64k FATX.
2. Large partition support (xbpartitioner-like) for F/G.
3. Displays the HDD model no besides the device name to ease identification of the hdd device.

Unzip the file to the usb flash drive to try it out.

xboxhd2 is still there for compatibility. The hdd locking retains xboxhdm2's functionality. I've used RMPrepUSB instead of Bootable USB-Drive Utility due to recent reports of issues.

So to be able to boot hdm3, the needed steps are?:
1 DL hdm3 & unpack
2 DL hdm3.02-addon & unpack to same dir as hdm3, overwrite
3 use RMPrepUSB to prepare USB
4 copy files from hdm3 to USB and overwrite

TRUE / FALSE ?

[spliff721]

i have never run into this problem, and somone else may have more info for you about this spacific problem. if i had to guess, i would say that some of the files used by XBOXHDM 1.9 are incompatable with 2.2. i know for a fact that there is a new NDURE script just for 2.2. so i am going to point you to a tutorial i made, and suggest that you start from scratch and rebuild the USB. just make sure to grab your eeprom.bin from the previous CD and put it in the EEPROM folder on the USB

here is the link to my guide.

http://forums.xbox-s...p;#entry4780448

[spliff721]

ha ha, thats what i get for not looking at dates before i respond. disregard my last post

in regards to your post, why not use XBOXHDM 2.2?

[ldotsfan]

hdm 2.2 + hdm3.0 addon = hdm3.0.

In all likelihood, hdm 3.0 doesn't work at all. A newer version doesn't mean anything at all - no support for hdm3.0 is planned and there's very little reported use of the tool. hdm2.2 is well tested and proven to work in many scenarios - for all practical reasons, stick to the older version if you don't want to thrash your hdd.

[ldotsfan]

It's surprising to hear that xboxhdm2.2 corrupted the files. I hope you used the right version packaged with RMPrepUSB instead of the earlier versions with other bootloaders.

Anyway good to know you have sorted things out