From mint-bounce@lists.fishpool.fi Tue Dec 8 04:24:14 2009 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=3uv0yYeB52N8K1Aa4LCcxXo2/d860DBdXaDrdH97GJs=; b=K6rz5ETK3PO8o58AYXHRrPMZrgsoxUxProLRpfyU/0SSHWQL/UWOwkBgWcGQynU+85 tJvSyli7lw5uCrB6XivLKe2Y/YtbQegr/B8JwmxPTeRf+gT6xNXk2DxH24FRWivEhifu +EQeF+AXg2Plt3D5Tr9Uh5u3PHkS1F14aWKok= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ad417rY8SPC05gUL4AKZjD3JNTlcRdswhGRqvYE0abR5GEGzrBXuJ0Do+6cgs9rZQY IpjjT0aQdHh5rT39pADn5EewI1GgHWj8v9N2wL1PnV3j8HCvFJ/rKzrsvsR6hv911IGE jnHh2N7j+OagGtgLB7hf+7belvkenA3Rad8jA= MIME-Version: 1.0 In-Reply-To: <11a6f2b10912080117k632b29f8x28e7577535acb975@mail.gmail.com> References: <11a6f2b10912080117k632b29f8x28e7577535acb975@mail.gmail.com> Date: Tue, 8 Dec 2009 10:21:50 +0100 Message-ID: Subject: Re: [MiNT] Getting drive names in XaAES From: Miro Kropacek To: Paul Wratt Cc: mint Content-Type: multipart/alternative; boundary=000325559a6aa1accd047a341a66 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: miro.kropacek@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: --000325559a6aa1accd047a341a66 Content-Type: text/plain; charset=ISO-8859-1 That means it takes ASCII value of 'a' (0x61) and adds a number to it (ranging from zero to N), i.e. you'll get values of ASCII codes for 'a', 'b', 'c', ... depending on what current drive number is. Then just adds ':' after this character resulting in "a:", "b:" etc strings. On Tue, Dec 8, 2009 at 10:17 AM, Paul Wratt wrote: > Can someone tell me why this happens: > *(info->home_path) = drv + 'a'; > *(info->home_path + 1) = ':'; > > or > defdir[0] = d_getdrv() + 'a'; > defdir[1] = ':'; > > > And is it "not restricted to XaAES" > > Cheers > > Paul > > > -- MiKRO / Mystic Bytes http://mikro.atari.org --000325559a6aa1accd047a341a66 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable That means it takes ASCII value of 'a' (0x61) and adds a number to = it (ranging from zero to N), i.e. you'll get values of ASCII codes for = 'a', 'b', 'c', ... depending on what current drive = number is. Then just adds ':' after this character resulting in &qu= ot;a:", "b:" etc strings.

On Tue, Dec 8, 2009 at 10:17 AM, Paul Wratt = <paul.wratt@gm= ail.com> wrote:
Can someone tell me why this happens:
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0*(info->home_path) =3D d= rv + 'a';
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0*(info->home_path + 1) = =3D ':';

or
=A0 =A0 =A0 =A0defdir[0] =3D d_getdrv() + 'a';
=A0 =A0 =A0 =A0defdir[1] =3D ':';


And is it "not restricted to XaAES"

Cheers

Paul





--
MiKRO / Mystic B= ytes
http://mikro.atari.org
--000325559a6aa1accd047a341a66--