PFS3aio and GVP A2000 HC+8 Series II

Overmann · 28 June 2018, 21:22

Hi there,

I am having some difficulty setting up PFS3 on my Amiga 2000. I have recently set it up on both my A1200 without issue (with CF cards), but on the 2000 the partitions simply won't mount.

I've tried using both HDinstTool and HDtoolbox, using both PDS\3 AND PFS\3, with 0x7FFFFFFe and 0xFFFFFE as masks, with 0x1FE00 as max transfer, made sure "automount" is checked but no partitions are mounted.

The A2000 has 3.1 roms and I am using 3.1 floppies. The scsi-controller has 8mb of ram and a 4.6gb HDD. I am attempting to create two partitions. One 1.3gb and one for the rest of the drive.
What am I missing? All suggestions are greatly appreciated!

wmsteele · 28 June 2018, 23:08

Are mask & max transfer not different for SCSI, for some reason I thinking 0xFFFFFFFF & 0x7FFFFFFF (mask & max). Might be wrong, its been a while!

Overmann · 28 June 2018, 23:15

The manual says nothing about max transfer as far as i can tell, but the mask numbers are lifted from the manual. As always I might have misunderstood and they might be wrong, but I can't find any other numbers.

I'll try your numbers

EDIT: Sadly, no partitions are mounted with those numbers either. Could there be something with the gvpscsi.device?

A4000Bear · 29 June 2018, 07:24

What version is your gvpscsi.device? You can find out by looking at what is printed on the sticker on top of the ROM or by typing in 'version gvpscsi.device' (without quotes).

Latest version is 4.15. I would guess that earlier versions would fail on drives that are even smaller than the OS 3.1 limit of 4GB.

thomas · 29 June 2018, 08:02

Did you add the file system in the partitioning program?

Did you give the file system the right identifier?

Both the file system and the partition must have the same identifier because the identifier is the connection between filesystem and partition.

Do not mix HDInstTools with other programs. HDInstTools will destroy the partiion table if you run it after another program. I'd suggest to stay with HDToolbox.

Read the PFS manual, too. It's in the PFS3_53 archive.

MaxTransfer can be set to 0x1fe00 everywhere, it does not really matter.

Mask should be taken from the GVP manual. A wrong mask can lead to performance issues.

Neither Mask nor MaxTransfer can cause that the partitions are not mounted.

With the PDS\3 variant the version of the driver should not matter unless it's so old that HD_SCSICMD is not supported.

Run this and attach the report here: http://thomas-rapp.homepage.t-online.../hddreport.lha

Overmann · 29 June 2018, 12:34

Quote:

Originally Posted by A4000Bear

What version is your gvpscsi.device? You can find out by looking at what is printed on the sticker on top of the ROM or by typing in 'version gvpscsi.device' (without quotes).

It appears I am on version 3.7. Thats a pretty long way off. Perhaps I should buy a chip and put the newest version on there. Can't hurt!

Quote:

Originally Posted by thomas

Did you add the file system in the partitioning program?

Did you give the file system the right identifier?

Both the file system and the partition must have the same identifier because the identifier is the connection between filesystem and partition.

Do not mix HDInstTools with other programs. HDInstTools will destroy the partiion table if you run it after another program. I'd suggest to stay with HDToolbox.

Read the PFS manual, too. It's in the PFS3_53 archive.

MaxTransfer can be set to 0x1fe00 everywhere, it does not really matter.

Mask should be taken from the GVP manual. A wrong mask can lead to performance issues.

Neither Mask nor MaxTransfer can cause that the partitions are not mounted.

With the PDS\3 variant the version of the driver should not matter unless it's so old that HD_SCSICMD is not supported.

Run this and attach the report here: http://thomas-rapp.homepage.t-online.../hddreport.lha

I've done it all over again now, taking care to follow your notes. Did it using HDtoolbox only. Put the FS in the program. Took care to use the correct identifier, set the maxtransfer to 0x1fe00 and used 0xFFFFFE as mask (though I'm not really sure how correct that is), I cant find any "THIS IS THE MASK" in the manual, just a mention that this should be sufficient for Series I. Mine is series II. :P

Here is the result from hddreport:

Code:

--------------------------------------------------------------------------------
Report generated by HDDReport version 1.29 on Friday, 29-Jun-18 at 12:00:05
--------------------------------------------------------------------------------

Overview:

  Drive      Volume         Capacity  Type  Boot  Device     Unit Loc.  Check
  DH0        Workbench3.1    1196 MB  PDS3     0  gvpscsi     0         ok
  DF0        PFS3             880 KB  DOS0     5< trackdisk   0         

--------------------------------------------------------------------------------
Report generated by HDDReport version 1.29 on Friday, 29-Jun-18 at 12:00:05
--------------------------------------------------------------------------------

System information:

  Kickstart 3.1         40.63             exec.library          40.10  
  dos.library           40.3              expansion.library     40.2   
  icon.library          40.1              graphics.library      40.24  
  intuition.library     40.85             utility.library       40.1   


CPU: 68000      FPU: none


Memory:

  Name                 Address      Size      Used      Free   Attributes
  expansion memory   $00200020   8192 KB    500 KB   7692 KB   PUBLIC, FAST, 24BITDMA, KICK
  chip memory        $00000420   1023 KB    114 KB    909 KB   PUBLIC, CHIP, LOCAL, 24BITDMA, KICK


Expansion boards:

  Bus  Board        Serial      Start     Size  Product                        Vendor
  Z2   2017/11   $EEEEEEEE  $00E90000    64 KB  SeriesII/HC8+ SCSI | I/O Ex... Great Valley Products
  Z2   2017/10   $EEEEEEEE  $00200000     8 MB  SeriesII RAM                   Great Valley Products

--------------------------------------------------------------------------------
Report generated by HDDReport version 1.29 on Friday, 29-Jun-18 at 12:00:05
--------------------------------------------------------------------------------

File Systems:

        DOS type    Name                           Size Version        Features
  PDS3  0x50445303  pfs3_aio.handler              64752  18.5   (Res)  TD64, NSD, SCSI
  DOS0  0x444F5300  ** no version tag found **

--------------------------------------------------------------------------------
Report generated by HDDReport version 1.29 on Friday, 29-Jun-18 at 12:00:05
--------------------------------------------------------------------------------

Exec Devices:

  clipboard.device                Version  38.8    (not a disk)
  console.device                  Version  40.2    (not a disk)
  gameport.device                 Version  40.1    (not a disk)
  input.device                    Version  40.1    (not a disk)
  keyboard.device                 Version  40.1    (not a disk)
  mfm.device                      Version  40.9    (not scanned)
  parallel.device                 Version  40.1    (not a disk)
  printer.device                  Version  39.6    (not a disk)
  ramdrive.device                 Version  39.35   (not scanned)
  serial.device                   Version  37.4    (not a disk)
  timer.device                    Version  39.4    (not a disk)

  gvpscsi.device        Unit   0  Version   3.7   SCSI

    TD_READ64        check failed with error -3 (command not supported by device)
    NSDCMD_TD_READ64 check failed with error -3 (command not supported by device)

    SCSI:
      Vendor       : HP      
      Product      : 4.26GB B 68-5520
      Revision     : 5520
      DeviceType   : Direct Access
      Removable    : no
      BlockAddress : 8330542
      BlockLength  : 512
      Capacity     : 4068 MB

    RDSK:                                  Flags:
      Vendor       : HP                      Last          = no
      Product      : 4.26GB B 68-5520        Last LUN      = yes
      Revision     : 5520                    Last TID      = no
      Cylinders    : 8330                    Reselect      = yes
      Sectors      : 200                     Disk ID       = valid
      Heads        : 5                       Controller ID = valid
      CylBlocks    : 1000                    Synch         = yes
      BlockBytes   : 512
      Capacity     : 4067 MB

    FSHD:
      PDS3  pfs3_aio.handler             Version  18.5   Size  69388 Bytes

    last readable block using CMD_READ:           8330542 (4068 MB)
    last readable block using HD_SCSICMD:         8330542 (4068 MB)
    last block contained in a DOS device:         2449999 (1196 MB)

  gvpscsi.device        Unit   2  Version   3.7   (none)

    NSDCMD_TD_READ64 check failed with error -3 (command not supported by device)

    SCSI:
      Vendor       : PLEXTOR 
      Product      : CD-ROM PX-40TS  
      Revision     : 1.05
      DeviceType   : CD-ROM
      Removable    : yes

  trackdisk.device      Unit   0  Version  40.1   (none)

    Geometry:
      SectorSize   : 512
      TotalSectors : 1760
      Cylinders    : 80
      CylSectors   : 22
      Heads        : 2
      TrackSectors : 11
      BufMemType   : PUBLIC
      DeviceType   : Direct Access
      Flags        : REMOVABLE
      Capacity     : 880 KB

    last block contained in a DOS device:            1759 ( 880 KB)

--------------------------------------------------------------------------------
Report generated by HDDReport version 1.29 on Friday, 29-Jun-18 at 12:00:05
--------------------------------------------------------------------------------

Partitions:

  DH0:
    Device          = gvpscsi.device       Flags:
    Unit            = 0                      Bootable = yes
    Flags           = 0                      Mount    = yes
    SectorSize      = 512
    Surfaces        = 5
    SectorsPerBlock = 1          /* 512 bytes */
    SectorsPerTrack = 200
    Reserved        = 2
    PreAlloc        = 0
    Interleave      = 0
    LowCyl          = 1
    HighCyl         = 2449       /* block 2449999 */
    Buffers         = 30
    BufMemType      = 0          /* ANY */
    MaxTransfer     = 0x0001FE00
    Mask            = 0x00FFFFFE
    BootPri         = 0
    DosType         = 0x50445303 /* PDS3 */

--------------------------------------------------------------------------------
Report generated by HDDReport version 1.29 on Friday, 29-Jun-18 at 12:00:05
--------------------------------------------------------------------------------

DOS Devices:


  DH0: /* Workbench3.1 */
    Device          = gvpscsi.device
    Unit            = 0
    Flags           = 0
    SectorSize      = 512
    Surfaces        = 5
    SectorsPerBlock = 1          /* 512 bytes */
    SectorsPerTrack = 200
    Reserved        = 2
    PreAlloc        = 0
    Interleave      = 0
    LowCyl          = 1
    HighCyl         = 2449       /* block 2449999 */
    Buffers         = 30
    BufMemType      = 0          /* ANY */
    MaxTransfer     = 0x0001FE00
    Mask            = 0x00FFFFFE
    BootPri         = 0
    DosType         = 0x50445303 /* PDS3 */

  DF0: /* PFS3 */
    Device          = trackdisk.device
    Unit            = 0
    Flags           = 0
    SectorSize      = 512
    Surfaces        = 2
    SectorsPerBlock = 1          /* 512 bytes */
    SectorsPerTrack = 11
    Reserved        = 2
    PreAlloc        = 0
    Interleave      = 0
    LowCyl          = 0
    HighCyl         = 79         /* block 1759 */
    Buffers         = 5
    BufMemType      = 1          /* PUBLIC */
    MaxTransfer     = 0x00200000
    Mask            = 0x7FFFFFFE
    BootPri         = 5
    DosType         = 0x444F5300 /* DOS0 */
    Baud            = 0
    Control         = 0

--------------------------------------------------------------------------------
End of report
--------------------------------------------------------------------------------

thomas · 30 June 2018, 07:44

The report shows one 1.2 GB partition which is mounted and formatted.

Does this mean your new attempt was successful? Or what else do you miss?

Overmann · 30 June 2018, 10:47

No still 100% unsuccessfull.

Nothing is getting mounted, and I have not formatted anything. Ihave not named a partition "Workbench 3.1". When I try to use pfsformat to format DH0: It tells me that it's unable to, or some such.

I am booting from 3.1 install and workbench here, and the only things on the desktop are the floppies and ram disk.

thomas · 30 June 2018, 12:52

What happens if you remove all floppy disks and reboot?

Overmann · 30 June 2018, 13:10

Quote:

Originally Posted by thomas

What happens if you remove all floppy disks and reboot?

At first the HDD light blinks steadily (about twice pr sec) for about 10 seconds, then the floppy drive starts steadily burping (about twice pr sec). It's been burping for a while now, but the screen is dark and unchanged.

EDIT:
I tried booting from Install3.1 now, instead of Workbench3.1, and running hddreport. The resulting report is the same as far as i can tell except that DH0: is now called "install3.1". So it names DH0: after the floppy it booted from it seems,

thomas · 30 June 2018, 13:42

Well, then run this program: http://thomas-rapp.homepage.t-online...ds/killrdb.lha

from a shell window like this:

killrdb gvpscsi.device 0

run it multiple time until it says "RDB not found".

It will change the RDSK identifier to RDSX so that the partition table cannot be found any more.

If you reboot now it should show the insert disk animation. You can then start with HDtoolbox from scratch.

utri007 · 30 June 2018, 13:57

Correct me if I'm wrong. HDtoolbox should install new filesystem to RDB? It seems to be a problem many cases. It is easily identified if you make a FFS partition for a boot partition and copy PFS to DH0:L\ everything should work now, but if you boot without startup-sequence only boot partition is accessable. <- that has been situation for me many cases.

I don't use SFS or PFS any more. FFS has lots of problems compared to SFS or PFS, but they are always solvable, when SFS or PFS problems are not.

Overmann · 30 June 2018, 16:24

@thomas
Ok, I've done that now, but it still never mounts DH0:. It appears that I run into exactly the same problems as before. I'm running the process again now from scratch and will try using HDinttool instead. I suspect it will not make a difference but it's worth a shot.

@utri007
I am not sure I understand you completely. Are you saying I should make a boot partition with FFS and then make a different partition with PFS to see if that works?

This is actually the first time I've had difficulties with PFS3. It has worked wonderfully for me before.

Could all this be because of my GVPSCSI.DEVICE 3.7? I've ordered new eproms and will install 4.15 when they arrive.

Toni Wilen · 30 June 2018, 17:07

Filesystem in L: has nothing to do with RDB installed filesystem and/or harddrive autobooting.

Toni Wilen · 30 June 2018, 18:48

I tested v3.7 GVP Series II ROM (thanks Overmann) in emulation and it seems to have broken RDB filesystem support.

Snipped from volume data (UAE debugger) with 3.7 (hangs):

00210300: Type=0 Port=00000000 Lock=00000000 'UDH0'
- H=00000000 Stack= 600 Pri=10 Start=00210330 Seg=00000000 GV=00000000
gvpscsi.device:0 000840d0

With 3.15 (boots normally):

00210c48: Type=0 Port=00202cfc Lock=00000000 'UDH0'
- H=00000000 Stack= 600 Pri=10 Start=00210c78 Seg=00210e4c GV=ffffffff
gvpscsi.device:0 00084322

Important difference is filesystem seglist pointer which is zero when using 3.7. (Tested with RDB hardfile, has one PFS3 partition)

Overmann · 30 June 2018, 21:32

Quote:

Originally Posted by Toni Wilen

I tested v3.7 GVP Series II ROM (thanks Overmann) in emulation and it seems to have broken RDB filesystem support.

Snipped from volume data (UAE debugger) with 3.7 (hangs):

00210300: Type=0 Port=00000000 Lock=00000000 'UDH0'
- H=00000000 Stack= 600 Pri=10 Start=00210330 Seg=00000000 GV=00000000
gvpscsi.device:0 000840d0

With 3.15 (boots normally):

00210c48: Type=0 Port=00202cfc Lock=00000000 'UDH0'
- H=00000000 Stack= 600 Pri=10 Start=00210c78 Seg=00210e4c GV=ffffffff
gvpscsi.device:0 00084322

Important difference is filesystem seglist pointer which is zero when using 3.7. (Tested with RDB hardfile, has one PFS3 partition)

Thats very interesting, thanks a lot! It seems the rom-upgrade is my solution then. I'll check back in here if I still have problems!
Thank you to everyone for taking the time to help me out!

Toni Wilen · 01 July 2018, 12:19

Yeah, ROM update should fix it.

Overmann · 16 July 2018, 23:56

Wow, brilliant! It worked! I now have two partitions of PFS3 up and running smoothly.
I do however get 100% cpu usage when reading and writing to disks. This is a mask issue, right? I don't understand mask or maxtransfer but i tried using 0xffffff and 0xfffff7. The first one did not improve things and the second gave me an error when booting.

Can anyone give me some tips as to what to use for this controller? The manual doesn't give it away.

I have it set up with 8mb of ram and my A2000 has 1mb of chip ram.

EDIT: Actually, come to think of it, I have owned scsi-controllers in the past and I don't think I've ever set one up correctly as I don't think I've ever used an amiga where the CPU didn't crawl while copying files or reading directories.

28 June 2018, 21:22	#1
Overmann Registered User Join Date: May 2014 Location: Norway Posts: 379	PFS3aio and GVP A2000 HC+8 Series II Hi there, I am having some difficulty setting up PFS3 on my Amiga 2000. I have recently set it up on both my A1200 without issue (with CF cards), but on the 2000 the partitions simply won't mount. I've tried using both HDinstTool and HDtoolbox, using both PDS\3 AND PFS\3, with 0x7FFFFFFe and 0xFFFFFE as masks, with 0x1FE00 as max transfer, made sure "automount" is checked but no partitions are mounted. The A2000 has 3.1 roms and I am using 3.1 floppies. The scsi-controller has 8mb of ram and a 4.6gb HDD. I am attempting to create two partitions. One 1.3gb and one for the rest of the drive. What am I missing? All suggestions are greatly appreciated! Last edited by Overmann; 28 June 2018 at 21:33.

28 June 2018, 23:15	#3
Overmann Registered User Join Date: May 2014 Location: Norway Posts: 379	The manual says nothing about max transfer as far as i can tell, but the mask numbers are lifted from the manual. As always I might have misunderstood and they might be wrong, but I can't find any other numbers. I'll try your numbers EDIT: Sadly, no partitions are mounted with those numbers either. Could there be something with the gvpscsi.device? Last edited by Overmann; 28 June 2018 at 23:25.

30 June 2018, 16:24	#13
Overmann Registered User Join Date: May 2014 Location: Norway Posts: 379	@thomas Ok, I've done that now, but it still never mounts DH0:. It appears that I run into exactly the same problems as before. I'm running the process again now from scratch and will try using HDinttool instead. I suspect it will not make a difference but it's worth a shot. @utri007 I am not sure I understand you completely. Are you saying I should make a boot partition with FFS and then make a different partition with PFS to see if that works? This is actually the first time I've had difficulties with PFS3. It has worked wonderfully for me before. Could all this be because of my GVPSCSI.DEVICE 3.7? I've ordered new eproms and will install 4.15 when they arrive. Last edited by Overmann; 30 June 2018 at 16:37.

16 July 2018, 23:56	#18
Overmann Registered User Join Date: May 2014 Location: Norway Posts: 379	Wow, brilliant! It worked! I now have two partitions of PFS3 up and running smoothly. I do however get 100% cpu usage when reading and writing to disks. This is a mask issue, right? I don't understand mask or maxtransfer but i tried using 0xffffff and 0xfffff7. The first one did not improve things and the second gave me an error when booting. Can anyone give me some tips as to what to use for this controller? The manual doesn't give it away. I have it set up with 8mb of ram and my A2000 has 1mb of chip ram. EDIT: Actually, come to think of it, I have owned scsi-controllers in the past and I don't think I've ever set one up correctly as I don't think I've ever used an amiga where the CPU didn't crawl while copying files or reading directories. Last edited by Overmann; 16 July 2018 at 23:59. Reason: Brainfart

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Help with GVP A2000-HC+8 Series II SCSI Card	checksum	support.Hardware	63	23 July 2019 09:12
Wanted GVP A2000-HC+8 Series II	A2666	MarketPlace	1	03 April 2016 02:56
GVP A2000-HC+8 Series II SCSI Card	Kin Hell	MarketPlace	8	20 May 2015 12:25
GVP Impact A2000-2B (Series 1?) jumper info	Jope	support.Hardware	2	14 July 2013 13:45
GVP Impact A2000-HC+8 Series II	Loedown	MarketPlace	0	13 April 2009 06:23

28 June 2018, 23:08	#2
wmsteele Registered User Join Date: Jul 2012 Location: Glasgow Posts: 128	Are mask & max transfer not different for SCSI, for some reason I thinking 0xFFFFFFFF & 0x7FFFFFFF (mask & max). Might be wrong, its been a while!

29 June 2018, 07:24	#4
A4000Bear Registered User Join Date: May 2011 Location: Taradale / Australia Posts: 95	What version is your gvpscsi.device? You can find out by looking at what is printed on the sticker on top of the ROM or by typing in 'version gvpscsi.device' (without quotes). Latest version is 4.15. I would guess that earlier versions would fail on drives that are even smaller than the OS 3.1 limit of 4GB.

29 June 2018, 08:02	#5
thomas Registered User Join Date: Jan 2002 Location: Germany Posts: 6,985	Did you add the file system in the partitioning program? Did you give the file system the right identifier? Both the file system and the partition must have the same identifier because the identifier is the connection between filesystem and partition. Do not mix HDInstTools with other programs. HDInstTools will destroy the partiion table if you run it after another program. I'd suggest to stay with HDToolbox. Read the PFS manual, too. It's in the PFS3_53 archive. MaxTransfer can be set to 0x1fe00 everywhere, it does not really matter. Mask should be taken from the GVP manual. A wrong mask can lead to performance issues. Neither Mask nor MaxTransfer can cause that the partitions are not mounted. With the PDS\3 variant the version of the driver should not matter unless it's so old that HD_SCSICMD is not supported. Run this and attach the report here: http://thomas-rapp.homepage.t-online.../hddreport.lha

30 June 2018, 07:44	#7
thomas Registered User Join Date: Jan 2002 Location: Germany Posts: 6,985	The report shows one 1.2 GB partition which is mounted and formatted. Does this mean your new attempt was successful? Or what else do you miss?

30 June 2018, 10:47	#8
Overmann Registered User Join Date: May 2014 Location: Norway Posts: 379	No still 100% unsuccessfull. Nothing is getting mounted, and I have not formatted anything. Ihave not named a partition "Workbench 3.1". When I try to use pfsformat to format DH0: It tells me that it's unable to, or some such. I am booting from 3.1 install and workbench here, and the only things on the desktop are the floppies and ram disk.

30 June 2018, 12:52	#9
thomas Registered User Join Date: Jan 2002 Location: Germany Posts: 6,985	What happens if you remove all floppy disks and reboot?

30 June 2018, 13:42	#11
thomas Registered User Join Date: Jan 2002 Location: Germany Posts: 6,985	Well, then run this program: http://thomas-rapp.homepage.t-online...ds/killrdb.lha from a shell window like this: killrdb gvpscsi.device 0 run it multiple time until it says "RDB not found". It will change the RDSK identifier to RDSX so that the partition table cannot be found any more. If you reboot now it should show the insert disk animation. You can then start with HDtoolbox from scratch.

30 June 2018, 13:57	#12
utri007 mä vaan Join Date: Nov 2001 Location: Finland Posts: 1,653	Correct me if I'm wrong. HDtoolbox should install new filesystem to RDB? It seems to be a problem many cases. It is easily identified if you make a FFS partition for a boot partition and copy PFS to DH0:L\ everything should work now, but if you boot without startup-sequence only boot partition is accessable. <- that has been situation for me many cases. I don't use SFS or PFS any more. FFS has lots of problems compared to SFS or PFS, but they are always solvable, when SFS or PFS problems are not.

30 June 2018, 17:07	#14
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,505	Filesystem in L: has nothing to do with RDB installed filesystem and/or harddrive autobooting.

30 June 2018, 18:48	#15
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,505	I tested v3.7 GVP Series II ROM (thanks Overmann) in emulation and it seems to have broken RDB filesystem support. Snipped from volume data (UAE debugger) with 3.7 (hangs): 00210300: Type=0 Port=00000000 Lock=00000000 'UDH0' - H=00000000 Stack= 600 Pri=10 Start=00210330 Seg=00000000 GV=00000000 gvpscsi.device:0 000840d0 With 3.15 (boots normally): 00210c48: Type=0 Port=00202cfc Lock=00000000 'UDH0' - H=00000000 Stack= 600 Pri=10 Start=00210c78 Seg=00210e4c GV=ffffffff gvpscsi.device:0 00084322 Important difference is filesystem seglist pointer which is zero when using 3.7. (Tested with RDB hardfile, has one PFS3 partition)

01 July 2018, 12:19	#17
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,505	Yeah, ROM update should fix it.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)