Look at the size of the file. If it is 399673 bytes big then it is okay and it's just the name which is wrong. In this case fix the name through the "copy" command. ie. "copy cd1:aros_pc_ sys:boot/aros-pc-i386.gz" or "copy cd1:aros_pc_ sys:boot/aros-xxx.gz" or "copy cd1:aros_pc_ sys:boot/aros-xxx-georg.gz" depending on what of the three ways described in the email I sent you, you prefer.

If the size of the file OTOH is 825332 then the file is not gzip compressed anymore, so something must have caused it to be uncompressed. Maybe when you saved it to hd from inside your email program? In this case you should compress it again with gzip. Which btw does not necessarily result in the compressed filesize of 399673 bytes mentioned above. It may differ depending on gzip version (I guess) and compression ratio.

Quote:
Did you receive your file through some Windows version?
Then Explorer is probably hiding the correct extension. Be sure to disable the "hide known extensions" option on File Browsing Configuration Panel. Remember that Explorer add or replace those extensions sometimes when the mime-type isn't fixed.

Well, GZ is a compression format. If you can run it through GZIP2 without breaking GZIP2, then yes, it could probably stand to benefit from a .GZ extension. (If it isn't a GZIP archive, then there's not much point to labelling it as such. Umm, most obnoxious shareware PC archivers handle GZIP now, if you'd rather not dig through your UNIX distribution tapes.)

I got your file.

It is named "aros-pc-i386"

No matter what I do Aros sees it as "aros_pc_" and it really doesn't like that.

All the others that I have seen end in ".gz" does this one need that extension?

Now on that "aros_pc_" thing. If I take out the Cd and put it back into windows it says "aros-pc-i386", put it back into Aros and it is "aros_pc_"

ooooohh, 400KBytes, you people have got to stop writing all this bloated code.


<end sarcasim>



:waaa:

Quote:

I think I know what's the problem there. If you want and know how to install it let me know (georg.steger@rolmail.net) and I send you an updated "rom" file (AROS/boot/aros-pc-i386.gz about 400 KByte big) to test.

Ahh but Mr Cat, such is not the case.

I simply used your scripts with the new CD, containing the updated files. Works like a charm.

well,

i saw you was upgranding some files for your nvidia issue...
well when you run the install script you "downgrade" again...so probably your nvidia is bad again...

if not, a fine search between the diferences of file should lead to the files involved in the issues (nvidia and hdtoolbox)

regards,

OK, the 12/12 build worked fine.

Also, I have resolved the issue!! Fist time I have resolved my own Aros issue!! Go Tech Support, Go Tech Support!!



Maybe not the best way, but I thought "why not?" With the Cd in I used CoolCats scripts, I ran the "onecore" and "install_grub" and, Volia! With the execption of my Warnderer backgroud all my previuos setting stayed. This surprised me but was great.

Also, still having strange Warnderer "rest" After booting the first time I click on anything Warnderer does a "reset" and then works fine. Strange...

Yes, If I boot from CD it is fine. I even tried running the HDtoolbox from the CD and the HDtoolbox from the HD. Both were fine when booting off the CD.

EDIT...

I should claify. I booted using Aros-Max. I am going to boot using the 12/12 build. Which by the way is the latest one... Nightlies went bye, bye again....