Tom Bruno (crweb | 21 Jan 01:04

Samba and XP support discussion. Where is the XP shares?


I'm starting a new discussion here to collect more information about
the non-visability of Microsoft Windows XP Home/Professional shares.

Things I need to know from users of linux and samba:

Can you view your windows XP shares in linux?
If you Can:
What linux distribution are you using?
Are you using DHCP?
Does your linux machine also have shares on it?
Did you manually setup a WINS server?
Is your machine the NIS server?
Are you hosting or part of a windows server domain?

Please attach your smb.conf if you ARE able to see Windows XP shares.

Current Status:
  I have setup a full network in house testing all the different angles
I can think of.  I do not have a formal solution that is both flash
firmware and reliable.  Size of the solutions, and the steps users have
to take on XP machines so far for solutions I do not find acceptable or
reasonable.  I will be posting these solutions soon

--~--~---------~--~----~------------~-------~--~----~
FOR REALTIME DISCUSSION GO TO IRC #neuros on freenode

You received this message because you are subscribed to the Google Groups "Neuros-DM320" group.
To post to this group, send email to Neuros-DM320Hardware <at> googlegroups.com
To unsubscribe from this group, send email to Neuros-DM320Hardware-unsubscribe <at> googlegroups.com
(Continue reading)

Kannaiyan Natesan | 21 Jan 12:38

Re: Samba and XP support discussion. Where is the XP shares?


> Can you view your windows XP shares in linux?
No.
Linux shares works but has a problem.

Another issue with Samba:

1. When I play with Media Player using the same samba share, it plays fine.
2. When I use OSD to play the same file, it creates a gap while
playing. I can see from the network indicator, the reading is
continious with Media Player but with OSD I can see the gap while
reading the file from samba.

Let me know if you need more information.

Regards,
Kannaiyan

On 1/21/07, Tom Bruno (crweb) <allyourrejects <at> gmail.com> wrote:
>
> I'm starting a new discussion here to collect more information about
> the non-visability of Microsoft Windows XP Home/Professional shares.
>
> Things I need to know from users of linux and samba:
>
> Can you view your windows XP shares in linux?
> If you Can:
> What linux distribution are you using?
> Are you using DHCP?
> Does your linux machine also have shares on it?
(Continue reading)

Kannaiyan Natesan | 21 Jan 14:12

Re: Samba and XP support discussion. Where is the XP shares?


Just a quick update.

When I connect the OSD to the router directly (which is also a hub) it
works fine. When I connect to one of the internal switch which is also
in the same network it did not work.

The file format which did give a jerk while playing is mpeg.

Regards,
Kannaiyan

On 1/21/07, Kannaiyan Natesan <gbpnkans <at> gmail.com> wrote:
> > Can you view your windows XP shares in linux?
> No.
> Linux shares works but has a problem.
>
> Another issue with Samba:
>
> 1. When I play with Media Player using the same samba share, it plays fine.
> 2. When I use OSD to play the same file, it creates a gap while
> playing. I can see from the network indicator, the reading is
> continious with Media Player but with OSD I can see the gap while
> reading the file from samba.
>
> Let me know if you need more information.
>
> Regards,
> Kannaiyan
>
(Continue reading)

Tom Bruno (crweb | 21 Jan 15:53

Re: Samba and XP support discussion. Where is the XP shares?


> Just a quick update.
>
> When I connect the OSD to the router directly (which is also a hub) it
> works fine. When I connect to one of the internal switch which is also
> in the same network it did not work.

It would be logical to think that the problem is the internal switch
hardware.  Can't really think of a reason why hub works, switch does
not work because switch activity should be faster than hub activity.
Is the pc with the samba share also connected to the hub or the switch?
 If it is connected to the hub then the switch might be bad.  If it is
connected to the switch, maybe the port you are plugging the OSD into
has went bad.

To me really sounds like a hardware failure on the network side. No way
to prove with little information, but this would be my first assumption
if trouble shooting myself.

--~--~---------~--~----~------------~-------~--~----~
FOR REALTIME DISCUSSION GO TO IRC #neuros on freenode

You received this message because you are subscribed to the Google Groups "Neuros-DM320" group.
To post to this group, send email to Neuros-DM320Hardware <at> googlegroups.com
To unsubscribe from this group, send email to Neuros-DM320Hardware-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/Neuros-DM320Hardware
-~----------~----~----~----~------~----~------~--~---

Kannaiyan Natesan | 21 Jan 16:26

Re: Samba and XP support discussion. Where is the XP shares?


PC (XP) -- Switch -- Hub (Router) -- Cable Modem

Don't have a guess how it worked.

If you need more info please feel free to ask.

Kannaiyan

On 1/21/07, Tom Bruno (crweb) <allyourrejects <at> gmail.com> wrote:
>
>
> > Just a quick update.
> >
> > When I connect the OSD to the router directly (which is also a hub) it
> > works fine. When I connect to one of the internal switch which is also
> > in the same network it did not work.
>
> It would be logical to think that the problem is the internal switch
> hardware.  Can't really think of a reason why hub works, switch does
> not work because switch activity should be faster than hub activity.
> Is the pc with the samba share also connected to the hub or the switch?
>  If it is connected to the hub then the switch might be bad.  If it is
> connected to the switch, maybe the port you are plugging the OSD into
> has went bad.
>
> To me really sounds like a hardware failure on the network side. No way
> to prove with little information, but this would be my first assumption
> if trouble shooting myself.
>
(Continue reading)

Tom Bruno (crweb | 21 Jan 16:43

Re: Samba and XP support discussion. Where is the XP shares?


On Jan 21, 9:26 am, "Kannaiyan Natesan" <gbpnk...@gmail.com> wrote:
> PC (XP) -- Switch -- Hub (Router) -- Cable Modem
>
> Don't have a guess how it worked.
>
> If you need more info please feel free to ask.

I would suggest trying connecting the OSD to different ports on the
switch and see if the problem continues.

--~--~---------~--~----~------------~-------~--~----~
FOR REALTIME DISCUSSION GO TO IRC #neuros on freenode

You received this message because you are subscribed to the Google Groups "Neuros-DM320" group.
To post to this group, send email to Neuros-DM320Hardware <at> googlegroups.com
To unsubscribe from this group, send email to Neuros-DM320Hardware-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/Neuros-DM320Hardware
-~----------~----~----~----~------~----~------~--~---

Kannaiyan Natesan | 22 Jan 08:55

Re: Samba and XP support discussion. Where is the XP shares?


On 1/21/07, Tom Bruno (crweb) <allyourrejects <at> gmail.com> wrote:
>
>
>
> On Jan 21, 9:26 am, "Kannaiyan Natesan" <gbpnk...@gmail.com> wrote:
> > PC (XP) -- Switch -- Hub (Router) -- Cable Modem
> >
> > Don't have a guess how it worked.
> >
> > If you need more info please feel free to ask.
>
> I would suggest trying connecting the OSD to different ports on the
> switch and see if the problem continues.

Connected in the way you said above. Did not work. Only along with the
router it works.
Here is the router link. (uPnP is also enabled, looks like it is for NAT)

http://www.planex.net/product/router/brl-04ur.htm

>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
FOR REALTIME DISCUSSION GO TO IRC #neuros on freenode

You received this message because you are subscribed to the Google Groups "Neuros-DM320" group.
(Continue reading)

Michael Gao | 24 Jan 12:47

Re: Samba and XP support discussion. Where is the XP shares?


On Sun, 2007-01-21 at 00:04 +0000, Tom Bruno (crweb) wrote:
> I'm starting a new discussion here to collect more information about
> the non-visability of Microsoft Windows XP Home/Professional shares.
> 
> Things I need to know from users of linux and samba:
> 
> Can you view your windows XP shares in linux?
> If you Can:
> What linux distribution are you using?
> Are you using DHCP?
> Does your linux machine also have shares on it?
> Did you manually setup a WINS server?
> Is your machine the NIS server?
> Are you hosting or part of a windows server domain?
> 
> Please attach your smb.conf if you ARE able to see Windows XP shares.
> 
> 
> Current Status:
>   I have setup a full network in house testing all the different angles
> I can think of.  I do not have a formal solution that is both flash
> firmware and reliable.  Size of the solutions, and the steps users have
> to take on XP machines so far for solutions I do not find acceptable or
> reasonable.  I will be posting these solutions soon
> 
> 
Tom, if there is any specific test that you need Xiamen team to help,
please let us know. 

(Continue reading)

jwu@neuros.com.cn | 25 Jan 07:36

Re: Samba and XP support discussion. Where is the XP shares?


http://lists.samba.org/archive/samba-technical/2004-December/038693.html

this is a way discussed before, But I tried the way it mentioned. OSD
and my PC still not work.
and another way is open the messange service in XP system so OSD can
find it. But this way is 
boring.

--~--~---------~--~----~------------~-------~--~----~
FOR REALTIME DISCUSSION GO TO IRC #neuros on freenode

You received this message because you are subscribed to the Google Groups "Neuros-DM320" group.
To post to this group, send email to Neuros-DM320Hardware <at> googlegroups.com
To unsubscribe from this group, send email to Neuros-DM320Hardware-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/Neuros-DM320Hardware
-~----------~----~----~----~------~----~------~--~---

jwu@neuros.com.cn | 25 Jan 07:43

Re: Samba and XP support discussion. Where is the XP shares?


I do not know if samba 4.0 can fix this bug?
samba website have samba 4.0 code.

--~--~---------~--~----~------------~-------~--~----~
FOR REALTIME DISCUSSION GO TO IRC #neuros on freenode

You received this message because you are subscribed to the Google Groups "Neuros-DM320" group.
To post to this group, send email to Neuros-DM320Hardware <at> googlegroups.com
To unsubscribe from this group, send email to Neuros-DM320Hardware-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/Neuros-DM320Hardware
-~----------~----~----~----~------~----~------~--~---

macroman | 27 Jan 06:35
Favicon

Re: Samba and XP support discussion. Where is the XP shares?


Note: I interpret "seeing Windows XP shares" to mean that I can use XP
to view shares exported by samba.  These shares reside on my Linux box.
 I'm running Slackware 10.2

>
> Can you view your windows XP shares in linux?
> If you Can:
> What linux distribution are you using?
I've had no problem (yet) viewing Windows XP shares in Linux.  I'm
using Slackware 10.x series.
> Are you using DHCP?
No.
> Does your linux machine also have shares on it?
Yes.  Also visible from both the OSD and my XP laptop.
> Did you manually setup a WINS server?
No.
> Is your machine the NIS server?
No - actually, I don't know for certain(!), but I didn't explicitly set
it up to be.  I used SWAT to configure my samba shares.
> Are you hosting or part of a windows server domain?
>
No.
> Please attach your smb.conf if you ARE able to see Windows XP shares.
# Samba config file created using SWAT
# from 127.0.0.1 (127.0.0.1)
# Date: 2007/01/26 22:40:59

# Global parameters
[global]
(Continue reading)

Tom Bruno | 27 Jan 07:57

Re: Samba and XP support discussion. Where is the XP shares?


> Linux box, but I remember being able to do it with something like
> "smb://user <at> ip/share-name" in Konqueror when I did have shares on an XP
> box. (I don't use XP for hosting anything anymore due to security
> concerns).
>
>   

Viewing shares using ip isn't the focus. Sorry I wasn't clear.  Of 
course you can always type the ip of the machine to access shares.  What 
we are actually looking for here is people that can "browse" the network 
just like you would "browse" in windows. 

The problem is that when we do a lookup for Windows XP names on the 
network using nmblookup (part of samba), XP machines don't show up.  IP 
is direct addressing the shares, and will always work.

Also, We don't need the shares section. We need the Global section of 
smb.conf's

Solutions have been found to get around the issue, I am still 
researching better methods.

Thanks :)

--~--~---------~--~----~------------~-------~--~----~
FOR REALTIME DISCUSSION GO TO IRC #neuros on freenode

You received this message because you are subscribed to the Google Groups "Neuros-DM320" group.
To post to this group, send email to Neuros-DM320Hardware <at> googlegroups.com
(Continue reading)

Nathan Crawford | 29 Jan 16:43
Favicon

Re: Samba and XP support discussion. Where is the XP shares?


--- Tom Bruno <allyourrejects <at> gmail.com> wrote:
> shares.  What 
> we are actually looking for here is people that can "browse"
> the network 
> just like you would "browse" in windows. 
> 
> The problem is that when we do a lookup for Windows XP names
> on the 
> network using nmblookup (part of samba), XP machines don't
> show up.  

FWIW: my Samba shares show up in the OSD without having to use
the full IP.  However, my Windows XP shares don't show up at
all.  Interestingly, I had to change the FS type in my smb.conf
to FAT before it would show up.  This might have something to do
with it, as you would need to be authenticated to view an NTFS
share, where with FAT, anyone can view it as long as it is
public.  So I suspect their are subtle differences in protocol
between viewing a public FAT share and a public NTFS share.

 
____________________________________________________________________________________
Cheap talk?
Check out Yahoo! Messenger's low PC-to-Phone call rates.
http://voice.yahoo.com

--~--~---------~--~----~------------~-------~--~----~
FOR REALTIME DISCUSSION GO TO IRC #neuros on freenode

(Continue reading)

Sco | 5 Feb 19:51

Re: Samba and XP support discussion. Where is the XP shares?


Curious on timing for a firmware update to incorporate XP networking
capability (2-way browsing)?

--~--~---------~--~----~------------~-------~--~----~
FOR REALTIME DISCUSSION GO TO IRC #neuros on freenode

You received this message because you are subscribed to the Google Groups "Neuros-DM320" group.
To post to this group, send email to Neuros-DM320Hardware <at> googlegroups.com
To unsubscribe from this group, send email to Neuros-DM320Hardware-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/Neuros-DM320Hardware
-~----------~----~----~----~------~----~------~--~---

Tom Bruno | 5 Feb 20:05

Re: Samba and XP support discussion. Where is the XP shares?


On 2/5/07, Sco <segould <at> gmail.com> wrote:

Curious on timing for a firmware update to incorporate XP networking
capability (2-way browsing)?



http://open.neurostechnology.com/node/754


--~--~---------~--~----~------------~-------~--~----~
FOR REALTIME DISCUSSION GO TO IRC #neuros on freenode

You received this message because you are subscribed to the Google Groups "Neuros-DM320" group.
To post to this group, send email to Neuros-DM320Hardware <at> googlegroups.com
To unsubscribe from this group, send email to Neuros-DM320Hardware-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/Neuros-DM320Hardware
-~----------~----~----~----~------~----~------~--~---

Michael Gao | 6 Feb 03:38

Re: Samba and XP support discussion. Where is the XP shares?


On Mon, 2007-02-05 at 13:05 -0600, Tom Bruno wrote:
> 
> On 2/5/07, Sco <segould <at> gmail.com> wrote:
>         
>         Curious on timing for a firmware update to incorporate XP
>         networking
>         capability (2-way browsing)?
>         
>         
> 
> http://open.neurostechnology.com/node/754
> 
Great!!

To continue the question, what should be done in order to include this
into the formal release?

And, I noticed you said that the current upk build process is broken,
what exactly were the problems you run into? build-helper.sh still is
able to build all the way to a developer upk.

Regards,

/MG

--~--~---------~--~----~------------~-------~--~----~
FOR REALTIME DISCUSSION GO TO IRC #neuros on freenode

You received this message because you are subscribed to the Google Groups "Neuros-DM320" group.
To post to this group, send email to Neuros-DM320Hardware <at> googlegroups.com
To unsubscribe from this group, send email to Neuros-DM320Hardware-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/Neuros-DM320Hardware
-~----------~----~----~----~------~----~------~--~---

Tom Bruno (crweb | 6 Feb 07:04

Re: Samba and XP support discussion. Where is the XP shares?


>
> To continue the question, what should be done in order to include this
> into the formal release?
>
> And, I noticed you said that the current upk build process is broken,
> what exactly were the problems you run into? build-helper.sh still is
> able to build all the way to a developer upk.

The problem isn't the upk build process.

Major problems that made this release difficult:

1.) Version number check.  I had to increase the version of my
firmware, or decrease the version stored in  cur_uboot, cur_kernel,
cur_rootfs. I could not flash alternative numbers, or lower version
numbers. This makes reflashing and testing difficult.

2.) I used 0.63 as my base, I had to name my firmware 0.64 to get it
to flash (see #1).  However the upk would still not flash because I
only included root.cramfs and uImage.  Error message was that I had to
update uboot.  This shouldn't not happen, i didn't need to include
uboot but the version checks made it so i had to.  Work around, i had
to go into the OSD and change cur_uboot to 0.64.  Forcing me to
include uboot is dangerous. changing cur_uboot is impossible without a
serial cable making my firmware useless to normal users and testers
without serial cable.

3.) Cannot reflash to official neuros firmware because of #1 and #2 my
versions are higher than Neuros versions.  Making it hard for users,
myself, and impossible again for non serial users to revert away from
custom firmware. (have to manually edit
cur_uboot,cur_kernel,cur_rootfs in OSD env)

4.) Cannot reflash my firmware after I messed it up. See #1, I messed
up some stuff and had to repack my rootfs.  I could not reflash 0.64 i
had to update my version to 0.65,  repeat #1, #2, #3.

The logic in flashing needs to be fixed.

--~--~---------~--~----~------------~-------~--~----~
FOR REALTIME DISCUSSION GO TO IRC #neuros on freenode

You received this message because you are subscribed to the Google Groups "Neuros-DM320" group.
To post to this group, send email to Neuros-DM320Hardware <at> googlegroups.com
To unsubscribe from this group, send email to Neuros-DM320Hardware-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/Neuros-DM320Hardware
-~----------~----~----~----~------~----~------~--~---

Michael Gao | 6 Feb 07:20

Re: Samba and XP support discussion. Where is the XP shares?


On Tue, 2007-02-06 at 06:04 +0000, Tom Bruno (crweb) wrote:
> >
> > To continue the question, what should be done in order to include this
> > into the formal release?
> >
> > And, I noticed you said that the current upk build process is broken,
> > what exactly were the problems you run into? build-helper.sh still is
> > able to build all the way to a developer upk.
> 
> The problem isn't the upk build process.
> 
> Major problems that made this release difficult:
> 
> 1.) Version number check.  I had to increase the version of my
> firmware, or decrease the version stored in  cur_uboot, cur_kernel,
> cur_rootfs. I could not flash alternative numbers, or lower version
> numbers. This makes reflashing and testing difficult.
> 
> 2.) I used 0.63 as my base, I had to name my firmware 0.64 to get it
> to flash (see #1).  However the upk would still not flash because I
> only included root.cramfs and uImage.  Error message was that I had to
> update uboot.  This shouldn't not happen, i didn't need to include
> uboot but the version checks made it so i had to.  Work around, i had
> to go into the OSD and change cur_uboot to 0.64.  Forcing me to
> include uboot is dangerous. changing cur_uboot is impossible without a
> serial cable making my firmware useless to normal users and testers
> without serial cable.
> 
> 3.) Cannot reflash to official neuros firmware because of #1 and #2 my
> versions are higher than Neuros versions.  Making it hard for users,
> myself, and impossible again for non serial users to revert away from
> custom firmware. (have to manually edit
> cur_uboot,cur_kernel,cur_rootfs in OSD env)
> 
> 4.) Cannot reflash my firmware after I messed it up. See #1, I messed
> up some stuff and had to repack my rootfs.  I could not reflash 0.64 i
> had to update my version to 0.65,  repeat #1, #2, #3.
> 
> The logic in flashing needs to be fixed.
Yes, the logic needs to be tighten up.

For now, you just need to use emergency upgrade with the backdoor, you
do NOT need to mess with the version number at all unless you want to,

1. rename your upk to r3.upk;
2. put it under [CF|SD|MS]/newpackage;
3. under /newpackage, create a dummy file called
'disable_upk_version_check'. 
4. recycle OSD power, it will ignore version and update.

/MG

--~--~---------~--~----~------------~-------~--~----~
FOR REALTIME DISCUSSION GO TO IRC #neuros on freenode

You received this message because you are subscribed to the Google Groups "Neuros-DM320" group.
To post to this group, send email to Neuros-DM320Hardware <at> googlegroups.com
To unsubscribe from this group, send email to Neuros-DM320Hardware-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/Neuros-DM320Hardware
-~----------~----~----~----~------~----~------~--~---

Tom Bruno (crweb | 17 Feb 00:04

Re: Samba and XP support discussion. Where is the XP shares?


> 1. rename your upk to r3.upk;
> 2. put it under [CF|SD|MS]/newpackage;
> 3. under /newpackage, create a dummy file called
> 'disable_upk_version_check'.
> 4. recycle OSD power, it will ignore version and update.
>
> /MG

Even with disable_upk_version_check   It still won't flash correctly.

U-Boot 1.1.4 (Feb 16 2007 - 15:52:14)

U-Boot code: 01400000 -> 0142ABB8  BSS: -> 0145F698
RAM Configuration:
Bank #0: 01100000 64 MB
Manuf. ID @ 0x00100000: 0x00000020
Device ID @ 0x00100001: 0x0000007e
Flash: 16 MB
In:    serial
Out:   serial
Err:   serial
DM320 Rev. B/C
initial i2c interface
Initializing Ethernet
found DM9000 at address 60000300:0x02 !
[eth_init]MAC:0:18:11:80:11:13:
Neuros Technologies OSD Controller (c) 2005
Ingenient Technologies NTSC/PAL Video Controller (c) 2005
Ingenient Technologies LCD Controller (c) 2005
Configuring video encoder for NTSC
CFG_FLAG_ADDR = 2300000
CFG_PACKAGE_ADDR = 2301000
Bus 0: OK
  Device 0: Model: SanDisk SDCFH-256  Firm: FhDA0145 Ser#:
0171101J04S30394
            Type: Removable Hard Disk
            Capacity: 245.0 MB = 0.2 GB (501760 x 512)
  Device 1: Bad status 0x0
not available
            newpackage/
            samba/
            etc/
  1806336   topiaboxdatabase.sql
    45608   bftpd
     9430   bftpd.conf
       40   run-ftpserver.sh
 14243872   w32codecs_20061022-0.0_i386.deb
 14521900   nvidia-linux-x86-1.0-9746-pkg1.run
            oldsamba/

6 file(s), 4 dir(s)

flag = 0
hack_falg
phdr->p_headsize: 104
phdr->p_reserve: 2
phdr->p_headcrc: 588a9ca1
phdr->p_datasize: 7742ea
phdr->p_datacrc: 31f66f92
phdr->p_name: r3.upk
phdr->p_vuboot: 0.00
phdr->p_vkernel: 0.00
phdr->p_vrootfs:
phdr->p_imagenum: 2
image correct
Hit any key to stop autoboot:  0
## Booting image at 00160000 ...
   Image Name:   Linux-2.6.15
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1213092 Bytes =  1.2 MB
   Load Address: 01108000
   Entry Point:  01108000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing
Linux................................................................................
Linux version 2.6.15 (pqiu <at> osdrls) (gcc version 3.4.6) #1 PREEMPT Fri
Feb 16 15:58:31 CST 2007
CPU: ARM926EJ-Sid(wb) [41069263] revision 3 (ARMv5TEJ)
Machine: IT DM320-20
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache

These are the same results I was seeing earlier.

Tom Bruno (crweb | 17 Feb 00:09

Re: Samba and XP support discussion. Where is the XP shares?


> 1. rename your upk to r3.upk;
> 2. put it under [CF|SD|MS]/newpackage;
> 3. under /newpackage, create a dummy file called
> 'disable_upk_version_check'.
> 4. recycle OSD power, it will ignore version and update.

The error was I need to update my uboot.

I didn't even put a uboot in my upk.  I dont want to damage uboot.
If i change the env  cur_uboot   to match my upk versions, it flashes
correctly.

disable_upk_version_check HAS to disable the uboot check also.

Needs fixing asap.

Michael Gao | 19 Feb 17:47

Re: Samba and XP support discussion. Where is the XP shares?


On Fri, 2007-02-16 at 23:09 +0000, Tom Bruno (crweb) wrote:
> > 1. rename your upk to r3.upk;
> > 2. put it under [CF|SD|MS]/newpackage;
> > 3. under /newpackage, create a dummy file called
> > 'disable_upk_version_check'.
> > 4. recycle OSD power, it will ignore version and update.
> 
> 
> The error was I need to update my uboot.
> 
> I didn't even put a uboot in my upk.  I dont want to damage uboot.
> If i change the env  cur_uboot   to match my upk versions, it flashes
> correctly.
> 
> disable_upk_version_check HAS to disable the uboot check also.
> 
> Needs fixing asap.
China team is on Chinese New Year holiday, will look into this after
2/25.

/MG


Gmane